Add Snapcraft metadata and install/maintenance hooks #666
Inga granskare
Etiketter
Inga etiketter
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 participant
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
No dependencies set.
Reference: Plume/Plume#666
Laddar…
Lägg till tabell
Hänvisa till i nytt ärende
No description provided.
Delete branch "add-snapcraft"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is somewhat of a proof of concept; it currently:
BASE_URL, addresses, and such throughsnap set plume base-url="blog.cooperteam.net"ROCKET_SECRETat install time, andEverything works, modulo the media upload directory not being configurable, and the base directory being read-only…
Codecov Report
Codecov Report
Codecov Report
Codecov Report
To test this you need to build the snap by running
snapcraftin a checkout; this should makeplume_0.3.0_amd64.snap(or whatever, as appropriate for your architecture). This can be installed withsudo snap install --dangerous plume_0.3.0_amd64.snap.Minimal setup is then something like:
(only sqlite is actually supported at the moment).
While the snap will run migrations on updates, you still need to manually do the initial migration, with something like:
sudo plume.plm migrate --path=/var/snap/plume/currentwhy is the installation
--dangerous?Because it's a local file (and you haven't pre-acknowledged its nonexistent signature), so it hasn't had any of the normal automated review. Once uploaded to the snap store that
--dangerouswill go away.(This is standard for installing locally-built snaps)
❓
why is this commented out?
what do we need / usr diesel-cli for?
Because I forgot to remove it, apparently!
The compile plume instructions say to install diesel_cli. Is that not necessary?
It would be good to fix this up so that the server doesn't try to start until setup the been completed. This was a manual attempt at doing that, but didn't quite work.
i don't think it's necessary.
@fdb-hiroshima?
It is for the 0.3.0 tag, but not for master (we have
plm migration runnow).Here is what I get when I run
snapcraft:(the french part are messages from git, nothing important)
I have snapcraft 2.43.1 and snap 2013-11-29-8, which seems quite old, maybe that is the issue?
Could this file go in the
snapdirectory too, or not?Maybe you are already aware of that, but just to have reminder: this description should probably be updated.
I think it can go in
snap/local. I'll give it a try.Done! Plume now doesn't try to run until it's been enabled, and doesn't let you enable it until you've set the minimum configuration items.
It can. Done!
Removed
Updated. Please give the verbiage a once-over!
This is now updated (sorry about leaving it hanging here). It definitely builds with snapcraft 3.8, 'cause that's what I've been using 😁
You now need to set all the configuration options (eg:
sudo snap set plume base-url=cooperteam.net db.type=sqlite) and then enable Plume (sudo snap set plume enabled=true). This will run the initial migrations, and so will be all ready to be configured withplume.plm ....👍