sitemap.xml
-
Hello everyone, where could I put a sitemap.xml for the mastodon app on cloudron ? Is it possible ? I already connect to ssh to find a folder "root" like the "www" with apache, but there is a yellowtent with appdata etc…If someone could help me with this…
cd /home/yellowtent/boxdata/appsdata/{app-name}/data/live/public/ -
On Cloudron all apps run in their own filesystem, which is for the most part read-only.
Use the webterminal from the dashboard to get a view of the app's filesystem. However only /app/data will be writable.For your sitemap.xml question, this won't work without either support the app itself or the app package.
I wasn't aware of the use-case for a sitemap for apps like mastodon, can you describe in a bit more detail what your plans are?
-
First of all thank you for your answers, I was just looking for a way to improve my mastodon's SEO but it's in progress apparently...I just have to be patient now…
Maybe it is an idea to package tools like this with mastodon? https://github.com/binfalse/mastodon-sitemap
Or fork this cloudron package and add this as well. Dunno. Just thinking.
-
Maybe it is an idea to package tools like this with mastodon? https://github.com/binfalse/mastodon-sitemap
Or fork this cloudron package and add this as well. Dunno. Just thinking.
@jaschaezra generally we try to stay as close as possible to mainline upstream, to avoid unexpected behavior and more importantly stay on the maintained packages. Too often forks or extra modules become abandoned, making it hard to update the package later on.
-
@jaschaezra generally we try to stay as close as possible to mainline upstream, to avoid unexpected behavior and more importantly stay on the maintained packages. Too often forks or extra modules become abandoned, making it hard to update the package later on.
@nebulon said in sitemap.xml:
@jaschaezra generally we try to stay as close as possible to mainline upstream, to avoid unexpected behavior and more importantly stay on the maintained packages. Too often forks or extra modules become abandoned, making it hard to update the package later on.
I do understand that but there is nearly no chance to add other tools as a server admin except forking the package and adding the missing stuff.
It would be great if there would be a way to add new stuff to an existing package without having the maintenance hassle. Like "add to existing app" or something like this.
-
@nebulon said in sitemap.xml:
@jaschaezra generally we try to stay as close as possible to mainline upstream, to avoid unexpected behavior and more importantly stay on the maintained packages. Too often forks or extra modules become abandoned, making it hard to update the package later on.
I do understand that but there is nearly no chance to add other tools as a server admin except forking the package and adding the missing stuff.
It would be great if there would be a way to add new stuff to an existing package without having the maintenance hassle. Like "add to existing app" or something like this.
@jaschaezra I understand the urge for this, however unless the app has a solid plugin or extension system for this, we can't really support this, as it will make it impossible for us to test for updates and thus will introduce another maintenance hassle on top, which in our experience leads to various side-effects which are hard to debug and cause quite a lot of support burden.
