Regular App Packaging Event

[doodlemania2]

@thetomester13 feel free to jump in on the repo if you'd like to help out - i can do it all, just haven't had the time. Whatever's left when we do the packaging event can be spent going through it from start to finish, talking about best practices (of which I am by no means the authority) and where we want to go from here.

[thetomester13]

@doodlemania2 tbh, I was hoping to go through it during the live session, debugging in tandem can be pretty powerful. That being said, if I get a chance between now and then, what hiccups exactly are you coming across? Haven't cloned it and ran it yet, but looks to be a good amount of the way there!

[doodlemania2]

@thetomester13 you bet - you're welcome of course to wait. No hiccups, just haven't had time to finish it and thought this might be a good one to get into the store.

[marcusquinn]

Good example of when having Croodle available would be good for polling preferred times & days

[bubonicfred]

@marcusquinn You can use the polls app in nextcloud and chuck out a public link, obviously not quite as simple as croodle, but nice if you are already using nextcloud

[thetomester13]

@marcusquinn one app at a time

[doodlemania2]

Time to rip the bandaid off!
I'll start at 3PM EST this Friday and broadcast for one hour. Might even record it if I can find a button for that. Will send out a link later in the week to this thread on how to join. Will walk through how I package, what I'm currently packaging and how (paperlessng), my current state, and where I'm currently at. Can crowdsource after the fact.

[jdaviescoates]

@doodlemania2 please do record! Would be great to get it up on https://videos.cloudron.io/

[ruihildt]

Here's to easily check what time it will be on your timezone:

https://www.timeanddate.com/worldclock/converter.html?iso=20210115T200000&p1=tz_et&p2=tz_cet

[thetomester13]

@doodlemania2 love it! I plan on being there and can try and help and chip in where needed!

[marcusquinn]

@doodlemania2 Great stuff, it's in my calendar and have asked a bunch of devs I work with to join hopefully.

[robi]

@marcusquinn said in Regular App Packaging Event:

Good example of when having Croodle available would be good for polling preferred times & days

Doesn't someone already have Croodle installed? I remember seeing it in the screen shots thread as a new unfamiliar icon.

Who wants to ping them to help us use it for this purpose?

[doodlemania2]

@robi I'm happy to use someone's Croodle, or, I can use my Jitsee meet (or cloudron's)

[jdaviescoates]

@doodlemania2 @robi @murgero has packaged it and has it installed here:

https://croodle.urgero.org/

[doodlemania2]

@jdaviescoates Can yall share? Would like to put it on my CR to play with prior to.

[jdaviescoates]

@doodlemania2 given I shared @murgero's demo install in my previous post, I guess you mean share the repo?

I just found this on git.cloudron.io:

https://git.cloudron.io/murgero/croodle-app

Hope that helps!

[doodlemania2]

@jdaviescoates oh yes, that's perfect - another plug for the "even before unstable" version of the app store hehe

[doodlemania2]

@doodlemania2 tried to cloudron build it:

100 13.0M 100 13.0M 0 0 4132k 0 0:00:03 0:00:03 --:--:-- 4132k
Removing intermediate container 6684e9348f66
---> 23d4aadc0809
Step 20/41 : ADD supervisor/ /etc/supervisor/conf.d/
---> 8328f9ec7f6b
Step 21/41 : RUN sed -e 's,^logfile=.*$,logfile=/run/supervisord.log,' -i /etc/supervisor/supervisord.conf
---> Running in 48ee763eaf86
Removing intermediate container 48ee763eaf86
---> d5bddbe7e79c
Step 22/41 : COPY start.sh config.php crontab.template credentials.template /app/code/
COPY failed: stat /var/snap/docker/common/var-lib-docker/tmp/docker-builder262714778/config.php: no such file or directory
child_process.js:669
throw err;
^

Error: Command failed: docker build -t doodlemania/croodle:20210112-194232-3228285bb -f Dockerfile /home/derek/croodle-app
at checkExecSyncError (child_process.js:629:11)
at execSync (child_process.js:666:13)
at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:180:5)
at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:327:9)
at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:256:9)

[girish]

@doodlemania2 That can sometimes happen if server ran out of disk space.

[doodlemania2]

@girish only at 24% used space... still looking - wondering if I'm on a different Ubuntu box version if that matters or something.