PackageDrone as Docker Container #68
Comments
Hi, the "admin" user token (and user name) can be overridden using a system property. I will look that up. The password is stored in the "users.json" file as well, just as a hashed and salted password, not in plaintext. The field is called "passwordHash" and "passwordSalt". I am not sure I fully understood the first question regarding the export channel? Maybe you can tell me what you are trying to do. In general what you can do is to setup up an instance of Package Drone and then copy over the plain file in the filesystem. It may be that this structure changes over releases, but in one release your would be safe. It is also possible to assign a "deploy" key to a channel and import a full channel (or multiple channels at once) using a HTTP request and a ZIP file. Also will there be a REST based API in the next version. But I am not sure if all features you need will be present. |
I did create wiki page about system properties [1]. You could use the system properties for setting the admin token, the name and the roles. So you would have exactly one user as you like it. [1] https://wiki.eclipse.org/PackageDrone/Configuration/SystemProperties |
@ctron Thanks for your support! The wiki was perfect for the admin user. Everything works perfect! I now can setup "default" channels signing keys for dev and have prod have it's NFS mounted volume for the data. Thanks for all support! |
Here's my (stripped Dockerfile). Cheers,
|
I did update your comment in order to format the Dockerfile correctly. I hope that is ok. So I think this one can be closed. |
Yes! Thanks again for all the support! Cheers, |
I’m currently packaging drone into a Docker Container – However I’ve stumbled into a problem. The only way of creating a “real” user is to use the web interface using the ‘admin’ and generated hash.
Is it possible to setup an environment export channel and import that while building the docker image via a command line?
Is it possible to provision a “default” user with password.
I’ve solved the user part jut {storage path}/users.json – but password seems to be put elsewhere.
Cheers,
Mario
The text was updated successfully, but these errors were encountered: