@robi Great idea. If my Mastodon keeps working fine without these, that would be so good. I've currently had to exclude it from my regular backups because of its size, and because sometimes the backup process would choke on some file and fail. I'll give that a go and report back.
@girish Great, I'll give it a try. Indeed, I need something like this because the size of my main Mastodon installation on Cloudron is already over 28GB! I've had to turn off Auto-Backup for it since it takes so long.
To me this seems like there is no clarity around domain vs storage location. We have two "locations" here. One is the external referenced location, which is the domain, where the app and thus the data is reachable. The second is the actual internal storage of data, which can be in various locations, like filesystem or database.
So the original inquiry here, at least to me, is mostly about the feeling that "Location" is somewhat related to data location internally within the server? The latter point would be the "Storage" tab in the app's configure view.
I personally would have never thought of changing the domain of an app to have any relation to destruction or losing of data, which to me makes this harder to understand. The domain for me is more like a public pointer.
I am more than happy to change the wording accordingly, we don't need to workaround here to limit the changes in wording.
@scooke Hello as far as I know you should have this running on WP multisite and thus moving it to Cloudron should be as easy as migrating any WP site.
That being said, it may depends on how you have set your multisite either using sub domains or sub directories. I'm running a multisite using sub directories on Cloudron for a few years without any problems.
There has been a few discussions here on the forum about the capacity of using it with sub domains, however I'm not sure if anything has ended up with a solution for this issue. Maybe, you can make a search for that on the forum, which I will check on myself as well as you remind us about it. 😳
It has made me all the more thankful for Cloudron, and how it's made Docker more accessible. I've previously used LAMP for my Wordpress, and only, thankfully, once before had a site hacked. Of course, that led to the whole LAMP setup being compromised. I did have backups then too, which helped, but man, seeing that hack spread through my LAMP was disheartening. I had tried to use Docker, and portainer, and such, but conceptually I just could never get more than 2 apps up and running and connected. I came across Cloudron... and voila, it all works, and the WP sites are all self-contained so that if one is hacked, the whole thing doesn't come crashing to a halt.
But about the original clone and build directory? Do I leave it, taking up space? Do I need it still?
You can delete it.
Buy if @nj decides to release an update you will have to clone it again, and build the update.
@BrutalBirdie Sure, I see that now. It was one of many assumed pieces of knowledge that I come across while trying to learn this stuff. It's assumed I will realize this is your server. One thing that definitely helped me misunderstand is the cloudron.dev bit... I initially thought that, ok, this is coming from cloudron somehow. Anyway, one hurdle hurdled. One good lesson learned. One detail I will be sure to highlight when I'm helping someone out.
Hmmmm I was thinking if I should do the example with placeholders so its more clear.
Next time placeholders will be used again to highlight the user needs to replace this part themself.
The second assumption was that I would know that the actual proper target
There is no 'proper' --target its your own decision how to name the target, I go with the id from the CloudronManifest.json.
like yours! (:0.0.1) or the BBB one (:1.0.20)
Because, again its your choice how the image is tagged.
cloudron build --help
Usage: cloudron build [options]
Build an app
--build-arg <namevalue> Build arg passed to docker. Can be used multiple times (default:
--build-service-token <token> Build service token
-f, --file <dockerfile> Name of the Dockerfile
--set-repository [repository url] Change the repository
--set-build-service [buildservice url] Set build service app URL
--local Build docker images locally
--no-cache Do not use cache
--no-push Do not push built image to registry
--raw Raw output build log
--tag <docker image tag> Docker image tag. Note that this does not include the repository
-h, --help display help for command
The --tag option lets you chose a tag instead of the cryptic hash.
For some of them, like Weblate, do you a way to see where traffic is coming from for them? Like, are there analytics indicating"Weblate searches are coming from companies, or universities, or research labs"? Do you have any targeted advertising for any of these apps on Cloudron, or has word-of-mouth in general been enough? Just curious, no need to spend any time looking it up.
I haven't checked recently but when we checked a couple of year ago, the basic analytics we had was not very useful in figuring this out. Given much of our crowd is fairly technical and privacy oriented, browsers+ad block addons strip the referrer header. This means we don't really know where they are coming from.
if you offer NextCloud as a service you CAN'T offer it with the name of NextCloud
Yes, I wanted to include something about this in my earlier reply, but then forgot about it. In this specific case its not much a problem of licenses, but rather about trademarks. If you run a modified version of one software, it may be in violation of their trademark to offer your version under the original name.
@scooke generally both CODE and OnlyOffice do not store anything persistently on the app itself. So given that you tried installing a fresh OnlyOffice instance altogether (uninstall+install) this issue might be more likely to be Nextcloud and their OnlyOffice connector related. So maybe look there for more info.
@robi Nope, I use my cloudron-supplied Vaultwarden to generate the secret, then I copy and paste it. I save it in a Secure Note in Bitwarden. The copy-and-paste is why I feel sure it wasn't a typo. Whatever the problem, it resolved itself. I restarted the app after each change, but maybe I didn't wait long enough for the startup to finish.
I've found OnlyOffice to be faster, especially if trying to collaboratively edit with others. This is because so much of the CODE stuff happens on the server rather than at the client end (although good to hear that's getting better @avatar1024 )
@jdaviescoates And it would be cool if the sign up page could be customizable, with an appearance like the Element sign up page (customizable image background) rather than a bland rectangular box sign up. Something that tells them... You are about to enter an incredible place!