Drone
-
@girish Thanks! Its here: https://git.cloudron.io/atridad/cloudron-drone-ci
-
@atridad I got it going here - https://git.cloudron.io/cloudron/drone-app/ . It seems the .env file is missing in the git repo, you should have permissions to add it.
@girish oh whoops, I’ll add that right away
-
@atridad I got it going here - https://git.cloudron.io/cloudron/drone-app/ . It seems the .env file is missing in the git repo, you should have permissions to add it.
@girish I work with macOS and because I cant import into your gitlab I copied and pasted the files into a new repo I made. Unfortunately the .env file is considered a hidden file and didn't show up in finder...
Good catch. Its in there now.
-
@girish I work with macOS and because I cant import into your gitlab I copied and pasted the files into a new repo I made. Unfortunately the .env file is considered a hidden file and didn't show up in finder...
Good catch. Its in there now.
-
@robi ahhh I'll check that out. I was being lazy tbh and didn't just use the command-line.
@atridad said in Drone:
I cant import into your gitlab I copied and pasted the files into a new repo I made
the next time you could also add an additional remote to your local repo and then push to this new remote. This has also the upside of preserving history.
-
@girish I work with macOS and because I cant import into your gitlab I copied and pasted the files into a new repo I made. Unfortunately the .env file is considered a hidden file and didn't show up in finder...
Good catch. Its in there now.
@atridad thanks!
Trying to understand how this app works. If I configure this for gitea, then it will use the gitea provider to sign in - https://docs.drone.io/server/provider/gitea/ ?
If that's the case, what is https://docs.drone.io/server/user/registration/ ? Or is the OAuth stuff separate from the users?
-
@atridad thanks!
Trying to understand how this app works. If I configure this for gitea, then it will use the gitea provider to sign in - https://docs.drone.io/server/provider/gitea/ ?
If that's the case, what is https://docs.drone.io/server/user/registration/ ? Or is the OAuth stuff separate from the users?
@girish The OAuth is seperate I believe. So far I haven't been able to see an issue with open registration. But yeah it uses gitea as a login provider.
-
@atridad said in Drone:
I cant import into your gitlab I copied and pasted the files into a new repo I made
the next time you could also add an additional remote to your local repo and then push to this new remote. This has also the upside of preserving history.
@fbartels Good point. I'll do that next time.
-
@atridad thanks!
Trying to understand how this app works. If I configure this for gitea, then it will use the gitea provider to sign in - https://docs.drone.io/server/provider/gitea/ ?
If that's the case, what is https://docs.drone.io/server/user/registration/ ? Or is the OAuth stuff separate from the users?
-
@fbartels Good point. I'll do that next time.
@atridad I had to add
RUN chmod +x /app/code/start.shto your Dockerfile in order to install it properly, it was throwing a 400 error.Is there any chance to add the runners/agents as cloudron apps as well? I was just playing around with the exec runner and couldn't get it to work, but I would think it could be the same as the cloudron-build-service, no?
-
@atridad I had to add
RUN chmod +x /app/code/start.shto your Dockerfile in order to install it properly, it was throwing a 400 error.Is there any chance to add the runners/agents as cloudron apps as well? I was just playing around with the exec runner and couldn't get it to work, but I would think it could be the same as the cloudron-build-service, no?
@msbt you don't really need an app for that, you can just run the docker runner on your cloudron host. I am using https://github.com/fbartels/cloudron-drone-app/blob/master/runner/docker-compose.yml along with a
.envfile with my server specific values. -
@msbt you don't really need an app for that, you can just run the docker runner on your cloudron host. I am using https://github.com/fbartels/cloudron-drone-app/blob/master/runner/docker-compose.yml along with a
.envfile with my server specific values.@fbartels I'm trying to have a complete deployment solution for static pages, like Directus + Gitea + Drone (with Agents) + Surfer on one server which can be given/rented to the customer when the site is finished, so they can have everything in one place and can build/update the website(s) themselves. Would be nice to have it in the GUI (and there's a dashboard on :3000 if you set credentials, right?) and have the possibility to restart if need arises without sshing onto the box. But if it's too tricky or crazy effort, your suggestion will probably be the way to go
-
@fbartels I'm trying to have a complete deployment solution for static pages, like Directus + Gitea + Drone (with Agents) + Surfer on one server which can be given/rented to the customer when the site is finished, so they can have everything in one place and can build/update the website(s) themselves. Would be nice to have it in the GUI (and there's a dashboard on :3000 if you set credentials, right?) and have the possibility to restart if need arises without sshing onto the box. But if it's too tricky or crazy effort, your suggestion will probably be the way to go
@msbt the webinterface on the runners is only for debugging as far as I know. So they do not really need to be reachable from the public internet. The only important thing is that the runners can reach the "dashboard" to get job information.
I have runners deployed on a few machines, even had it running on my laptop.
And one of the Drone jobs indeed builds a hugo blog and then deploys it via surfer.
-
@msbt the webinterface on the runners is only for debugging as far as I know. So they do not really need to be reachable from the public internet. The only important thing is that the runners can reach the "dashboard" to get job information.
I have runners deployed on a few machines, even had it running on my laptop.
And one of the Drone jobs indeed builds a hugo blog and then deploys it via surfer.
@fbartels thanks, it does work indeed, I even used your
cloudron-surferimage to deploy a demo Hugo to a surfer instance.Although I would still find it a lot more practical if the runner was an actual part of cloudron, so we go full circle and have all the benefits, like when you migrate everything on a new machine
-
@fbartels thanks, it does work indeed, I even used your
cloudron-surferimage to deploy a demo Hugo to a surfer instance.Although I would still find it a lot more practical if the runner was an actual part of cloudron, so we go full circle and have all the benefits, like when you migrate everything on a new machine
@msbt True. The best part about runners though is that they need barely any config and don't need to store much at all. It is very scalable. As for my image, I do need to fix that. I've been slammed with projects and life lately but I'm trying to get to everything I've said I would do lol
-
@msbt True. The best part about runners though is that they need barely any config and don't need to store much at all. It is very scalable. As for my image, I do need to fix that. I've been slammed with projects and life lately but I'm trying to get to everything I've said I would do lol
@atridad If you detail out some steps of what needs doing, perhaps someone can chip in at the repo you specify.
Many hands make short work.
-
@atridad If you detail out some steps of what needs doing, perhaps someone can chip in at the repo you specify.
Many hands make short work.
-
@robi from my perspective that is all already part of https://github.com/fbartels/cloudron-drone-app/. Atridad just decided that he wanted to do his own app.
-
@atridad If you detail out some steps of what needs doing, perhaps someone can chip in at the repo you specify.
Many hands make short work.
@robi Just added that. Thing about this repo is hopefully making it more viable as an official app. One thing that I think would help is support for required environment variables when installing specific apps. Similar to how the ports are defined. That would let us specify the gitea URL and the OAuth info.
