Cloudron as an app inside of Cloudron

[Lonkle]

@BrutalBirdie Do you make box changes as well?

[BrutalBirdie]

@Lonk said in Cloudron as an app inside of Cloudron:

@BrutalBirdie Do you make box changes as well?

No, I did not yet contribute to the cloudron "base" itself.
So I don't know what pains you are going threw

pain >

But I’ve been using ssh -> nano to make all my box changes so I didn’t have to reinstall every change and it’s just really cumbersome.

[Lonkle]

@mehdi said in Cloudron as an app inside of Cloudron:

I would theoretically be possible, I think, but honestly it would be an infrastructure nightmare to set-up. My opinion => don't go this route, use proper VMs. In addition to being much easier to accomplish, you'll also get an environment much closer to an actual cloudron, so there will be much less weird different behaviours.

You mentioned this before. Since this is just for testing new box code quickly with the same flow as a custom app. Do you still think it’s more work than it’s worth? Infrastructure nightmare is particularly what I’m confused about; I want to understand what you mean by that.

[Lonkle]

@BrutalBirdie said in Cloudron as an app inside of Cloudron:

pain >

But I’ve been using ssh -> nano to make all my box changes so I didn’t have to reinstall every change and it’s just really cumbersome.

Not gonna lie, it feels like I’m coding in the 90s whenever I use nano. You can’t even select text. Every character has to be deleted one by one. It’s faster than constantly recompiling and re-installing on Ubuntu 18.04. But slower than just about anything else.

[girish]

@Lonk Are you already using the hotfix script? https://git.cloudron.io/cloudron/box/#development This is what we use for development.

[Lonkle]

@girish said in Cloudron as an app inside of Cloudron:

@Lonk Are you already using the hotfix script? https://git.cloudron.io/cloudron/box/#development This is what we use for development.

This looks like a godsend. I just have to figure out how to format hot fixes and use this CLI tool to apply them to my virtual machine Cloudron. Thank you for showing me this!

Also, I saw in that description in your link: “front-end code click here” and it was 404 .

But using this hot fix tool I might be able to contribute to dashboard easier (like the drop down box to choose the vpnclient to connect to).

[girish]

@Lonk said in Cloudron as an app inside of Cloudron:

Also, I saw in that description in your link: “front-end code click here” and it was 404 .

Are you logged into GitLab? I feel like I have solved this permission/visibility issue in GitLab like a million times. I am not sure what GitLab is doing but that setting gets reset of something after each update

[Lonkle]

@girish I clicked on the "click here" link which lead to this:

https://git.cloudron.io/cloudron/dashboard

It asked me to log in, which I did (as Lonk), and it lead to a 404. So I tried clicking it again thinking it could have been a login redirection issue and I'm fully logged in now, and it still says 404.

[robi]

If you want to try and get this going, here are a few rough steps.

• Install sysbox from Nestybox and validate you can spin up containers with sysbox-runc
• Get a small Ubuntu 18.04 image running inside
• Validate networking in and out for basic services
• Install the inner Cloudron and see how to set up DNS and ports so it works for the inner and outter Cloudrons separately.
• Document the kinks

Once this is running, you'll have a base container system image which is special and can run as an App.

It may be useful to set up guacamole as remote desktop access.

Feel free to chime in and add to my list.

[Lonkle]

@robi I plan on contributing more here so I'll try both yours and @girish's hot fix dev methods and see which one works better for me.

I genuinely appreciate you taking the time to put those steps together for me. Thank you! ️

[Lonkle]

@girish cloudron machine says it's not an available command. Though it's documented to be so in the npm main database. https://www.npmjs.com/package/cloudron

Do I need to load on top of my already existing cloudron cli tool?

[girish]

@Lonk It's a separate repo and a separate tool - https://git.cloudron.io/cloudron/cloudron-machine . If you clone and do "npm link . ", it is available in your PATH.

[Lonkle]

@girish said in Cloudron as an app inside of Cloudron:

@Lonk It's a separate repo and a separate tool - https://git.cloudron.io/cloudron/cloudron-machine . If you clone and do "npm link . ", it is available in your PATH.

Joel$ cloudron-machine
Usage:  [options] [command]

Options:
  -V, --version            output the version number
  -h, --help               output usage information

Commands:
  hotfix [options]         Hotfix Cloudron with latest code
  ssh [options] [cmds...]  Get a remote SSH connection

Ah, I understand, you should fix that in the npm repository description cause I was so confused for a second. Thank you very much for taking the time to write out instructions in how to get the actual tool. ️

But both the commands hotfix and ssh error out instead of displaying manuals. Are there manuals to those commands? Or maybe an example of a hotfix option and ssh option (using fake data of course)?

[Lonkle]

@girish Like your cloudron build --no-push hot fix that you've already uploaded to master, how could I apply that with this tool?

[Lonkle]

I think I get it actually. I supply it the whole cloudron installation with all the hotfixes at once and it overwrites the appropriate files with the ssh commands I give it. Still figuring out the syntax though.

[Lonkle]

I've only ever logged in via password but I have to use files for the ssh I give it I think. And I must have to be in the root of the cloudron box I'm hotfixing:

SSH_PASSPHRASE=sshkeypassword cloudron-machine hotfix --cloudron my.example.com --release 6.0.0 --ssh-key keyname

[Lonkle]

@girish I still haven't figured out what hotfix is in the documentation (I think it's a directory of cloudron files) and this app has no manuals.

[Lonkle]

@girish I've re-installed Cloudron. I'm assuming I run this cloudron-machine hot fix CLI before I set anything up because it goes in via SSH and does it's thing?

I just can't tell the syntax and what hotfix is in the syntax? Is it a directory of all the changed yellowtent files in which case it overwrites them? Should I start the folder structure at /yellowtent/ or /box/?

[nebulon]

The hotfix command currently is really only used and thus tailored to @girish and my use-case. It used to be part of the normal cli tooling, but since it requires a specific folder setup of box and dashboard repo we removed it from there.

In order to make it useful for more people, I think we have to rework that quite a bit.

[Lonkle]

@nebulon said in Cloudron as an app inside of Cloudron:

It used to be part of the normal cli tooling

Yeah, it's still documented in the npm repo as cloudron machine for the normal CLI.

But it would really help me with updates and applying my hot fixes (one in development made by @girish that's already in master but not released, and the other my VPN Client hot fixes until @girish is ready to work with me to integrate them into core in 2021).

Basically, @nebulon, is there anyway I can use this tool? @girish acted as if it was the perfect tool to use in my case. Because every update I have to SSH into the server and nano ../home/yellowtent/box/src/docker.js along with 3 other files to keep testing my app every time you guys update (it's treacherous, you can't even select text in nano every change has to be manually redone). Soooo, is it possible for me to use this tool to do that?

Also, @girish told me I should have permission to see the dashboard repo (the VPN client needs a dropbox in every app's dashboard config to choose which VPN Client to connect to) but it returns a 404 even when logged in (which @girish said was a bug a few posts above this one).

I figured the CLI required an exact folder format. I was guessing the entire installation of Cloudron /yellowtent/box/ pulled from the server. I then make my hot fixes (including girish's --no-push hot fix from master). And the hotfix tool took the SSH credentials and did diffs to compare and overwrite as needed.

Am I close? This tool is very undocumented but girish made it sound like it was needed for me (probably felt bad I was using nano via ssh).