Based on their roadmap, it appears that there are two new features in the works:

1. Integrating with self-hosted GitHub Actions runners,
2. Storing and managing personal/organisation secrets.

Looking forward to the 1.15 release!

@nebulon Since ipv4 addresses are getting more expensive it might be worthwhile to start considering and planning for ipv6.

I use RStudio for spatial data analysis, dashboard creation, and generating reports. Would be nice to see it on Cloudron.

For those using Hetzner, it seems that they have released IPv6-only versions for some of their dedicated servers. These IPv6-only servers are cheaper since the price of the IPv4 address is deducted from the original price.

More info can be found here https://docs.hetzner.com/robot/dedicated-server/ip/faq-primary-ipv4/.

They are apparently working on IPv6-only cloud servers as well, so it's something to look forward to if Cloudron can support IPv6.

@loudlemur As far as I know Cloudron installations are only for Ubuntu. This is just the CLI to interact with your Cloudron that you install on an Ubuntu machine, if you use a computer that runs Windows.

I've tried out HomelabOS and agree with @jdaviescoates assessment. Installation of apps on Cloudron is smoother, especially considering some features such as email and user/group management are ready for use. Installing apps, setting scheduled backups and mounting volumes from the UI is also a nice touch. For HomelabOS, I believe the installation of apps and other HomelabOS-specific functions are done through the command line, which may not appeal to everyone.

However, HomeLabOS has its advantages in the sense that there are some apps on HomeLabOS which are not available on Cloudron (e.g. Miniflux), so it also depends on your requirements - does HomelabOS or Cloudron have the app you want?.

Both are very active projects and have made lots of improvements over the past few months, and I made the decision to go with Cloudron.

@robi I'm installing this on Nexus Bytes' vDedi (Singapore location) and using their official Ubuntu 20.04 image.

I created the file using touch /var/log/journal/*/system.journal and ran ./cloudron-setup again and it's all good.

Thanks for the quick fix, and Merry Christmas.

@timconsidine Thanks for the great piece of info! I didn't know AWS can see if sandbox testing was done or not. In my experience, AWS seems seems to be getting stricter with granting production access to SES. They also look at how you monitor and manage bounces and complaints and whether you are setting any limits for the bounce rate and complaint rate.

@hollosch I also received that email response when I applied for SES production access last month. What I did was that I also had to tell them how I was tracking the bounce and complaint rates:

• using the metrics dashboard in the Console
• setting up the alerts and notifications with SNS (https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-activity-using-notifications-sns.html)
• telling them what my bounce rate and complaint rate limits are (I just followed what they mentioned in the SES docs for this one)

in addition to what was already mentioned by @timconsidine. I also did the sandbox testing to verify if my SNS notifications work.

While this has worked for me, I can't guarantee if it'll work for you because there could be other factors involved in the approval process I'm not aware of. Hope this helps!

@scooke Let's go through each question.

How in the world would someone find this domain, to begin with. And secondly, why would someone use/send my domain when they don't have access?

Email addresses are like addresses for physical mail; as long as you know what the address is, and the address is valid, the mail will be delivered.

The email was spam, so was some bot simply trawling for domains and then adding various names to it to make an email, hoping it gets to someone real?

Or, in another case, someone else signed up for some financial services, but used my domain??!! Why would they do that? So i'm getting their emails.

Depending on the content of the email, it can be either of the two cases you mentioned. Why would someone sign up for something using your domain? Maybe they thought of using yours as a "disposable email address" or they got blacklisted from using their own and had to use someone else's.

I've considered blocking them, or sending them to Junk, BUT, wouldn't this be hurting myself? If I say mail from my own domain, or to my own domain, is spam, won't my overall email deliverability get affected?

Overall email deliverability will be affected if you send spam, not receive it. So I don't think marking those emails sent to your domain will affect it.

@timconsidine Thanks for the great piece of info! I didn't know AWS can see if sandbox testing was done or not. In my experience, AWS seems seems to be getting stricter with granting production access to SES. They also look at how you monitor and manage bounces and complaints and whether you are setting any limits for the bounce rate and complaint rate.

@hollosch I also received that email response when I applied for SES production access last month. What I did was that I also had to tell them how I was tracking the bounce and complaint rates:

• using the metrics dashboard in the Console
• setting up the alerts and notifications with SNS (https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-activity-using-notifications-sns.html)
• telling them what my bounce rate and complaint rate limits are (I just followed what they mentioned in the SES docs for this one)

in addition to what was already mentioned by @timconsidine. I also did the sandbox testing to verify if my SNS notifications work.

While this has worked for me, I can't guarantee if it'll work for you because there could be other factors involved in the approval process I'm not aware of. Hope this helps!

For those using Hetzner, it seems that they have released IPv6-only versions for some of their dedicated servers. These IPv6-only servers are cheaper since the price of the IPv4 address is deducted from the original price.

More info can be found here https://docs.hetzner.com/robot/dedicated-server/ip/faq-primary-ipv4/.

They are apparently working on IPv6-only cloud servers as well, so it's something to look forward to if Cloudron can support IPv6.

@nebulon Since ipv4 addresses are getting more expensive it might be worthwhile to start considering and planning for ipv6.

@loudlemur As far as I know Cloudron installations are only for Ubuntu. This is just the CLI to interact with your Cloudron that you install on an Ubuntu machine, if you use a computer that runs Windows.

Based on their roadmap, it appears that there are two new features in the works:

1. Integrating with self-hosted GitHub Actions runners,
2. Storing and managing personal/organisation secrets.

Looking forward to the 1.15 release!

@girish Thanks for the answer. Having one and only one environment per user is quite the inconvenience

@scooke Let's go through each question.

How in the world would someone find this domain, to begin with. And secondly, why would someone use/send my domain when they don't have access?

Email addresses are like addresses for physical mail; as long as you know what the address is, and the address is valid, the mail will be delivered.

The email was spam, so was some bot simply trawling for domains and then adding various names to it to make an email, hoping it gets to someone real?

Or, in another case, someone else signed up for some financial services, but used my domain??!! Why would they do that? So i'm getting their emails.

Depending on the content of the email, it can be either of the two cases you mentioned. Why would someone sign up for something using your domain? Maybe they thought of using yours as a "disposable email address" or they got blacklisted from using their own and had to use someone else's.

I've considered blocking them, or sending them to Junk, BUT, wouldn't this be hurting myself? If I say mail from my own domain, or to my own domain, is spam, won't my overall email deliverability get affected?

Overall email deliverability will be affected if you send spam, not receive it. So I don't think marking those emails sent to your domain will affect it.

@girish I see.

From what I understand, each user has a virtual environment of their own. Each user can install their own packages using the notebook itself, and not the terminal.

That means that if a user were to have multiple virtual environments, then I would need to set it up using ipykernel via the notebook too?

@robi I'm not able to install them because they still want to install it in the read-only directories for the base env. If I create an virtual environment using venv, I also won't be able to choose it as the kernel since there is no root system access.

Not sure if I'm missing something.

Is it possible to install external python libraries using pip via the terminal?