Hello there!
Just wondering if there is a special thread where Rockons requests are gathered, so that it could be easier to track if a container is either undergoing or not getting developed at all yet.
I’m asking this, because I wanted to request a Mealie Rockon, which I believe it would be pretty useful!
Thanks!!
@sanviler on the forum there is no dedicated thread for it at this time. Of course, it never hurts to ask whether someone has already created a Rockon configuration for themselves of a particular product, and just not created a submission on github for it.
But, for a more formally tracked request, you can open one on github directly (you do need to have a github account on there, though). You can check whether theres already a request out there.
If you open a request, it would be great if you could link to the project for which you’re requesting it, and what a primary use case would be. That give people a better sense of whether that’s something they want to work on and publish.
Obviously, if you’re game, you’re more than welcome to fulfill your own request 
. You could read the Read Me on the github repository and see whether you’re able to come up with your own configuration file. There are some additional tips that can be found here under the [community contributions documentation].(Contributing a Rock-on — Rockstor documentation)
Hey, thanks for the reply. Guess it is a great idea to interact directly on the github repo for this. Absolutely! There’s not much to link thou, since it is just something I thought to add to my home-network server/storage: got an smb and nfs shared pool and a couple rock-on streaming services (jellyfin and airsonic). Wanted to add Mealie to that stack 
Will also look into trying implementing one, maybe experimenting a bit on a virtual machine, since I’m afraid to mess with my storage and lose everything.
Thanks a lot for the support!
Since this looked like an interesting distraction, I created a minimal version of this. I installed it and it seems to work just fine this way. The only thing I omitted was the Base_url parameter, assuming it’s really for the home network or any other proxying will connect directly to it. I also picked postgres as the backend database, since it sees to enable more functionality and is recommended by them in the documentation when running on a NAS…
So, here it is:
{
"Mealie": {
"description": "Mealie is a self-hosted recipe manager and meal planner with a REST API backend and a reactive frontend application built in Vue for a pleasant user experience for the whole family.</p><p>Based on the <a href='https://github.com/mealie-recipes/mealie/pkgs/container/mealie' target='_blank'>official OCI image</a>, available for amd64 and arm64 architecture.</p>",
"version": "1.0",
"website": "https://mealie.io/",
"ui": {
"slug": ""
},
"containers": {
"mealie-db": {
"image": "postgres",
"tag": "17",
"launch_order": 1,
"volumes": {
"/var/lib/postgresql/data": {
"description": "Database storage for Mealie (Postgres).",
"label": "Database storage [e.g. mealie-pgdata]"
}
},
"environment": {
"POSTGRES_USER": {
"description": "Set the username for the postgres user.",
"label": "Postgres user [e.g. mealie]"
},
"POSTGRES_PASSWORD": {
"description": "Set the password for the postgres user.",
"label": "Postgres password [e.g. mealie]"
},
"POSTGRES_DB": {
"description": "Set the database name.",
"label": "Database name [e.g. mealie]"
}
}
},
"mealie-app": {
"image": "ghcr.io/mealie-recipes/mealie",
"tag": "latest",
"launch_order": 2,
"ports": {
"9000": {
"description": "Mealie Web Interface port.",
"label": "WebUI port [e.g. 9925]",
"host_default": 9925,
"protocol": "tcp",
"ui": true
}
},
"volumes": {
"/app/data/": {
"description": "Data storage for Mealie application.",
"label": "Mealie data [e.g. mealie-data]"
}
},
"opts": [
[
"-e",
"DB_ENGINE=postgres"
],
[
"-e",
"POSTGRES_SERVER=mealie-db"
],
[
"-e",
"POSTGRES_PORT=5432"
]
],
"environment": {
"ALLOW_SIGNUP": {
"description": "Allow new user registrations.",
"label": "Allow signup [e.g. false]"
},
"PUID": {
"description": "User ID to run the container as.",
"label": "PUID [e.g. 1000]"
},
"PGID": {
"description": "Group ID to run the container as.",
"label": "PGID [e.g. 1000]"
},
"POSTGRES_USER": {
"description": "Must match the database username set in mealie-db.",
"label": "Postgres user [e.g. mealie]"
},
"POSTGRES_PASSWORD": {
"description": "Must match the database password set in mealie-db.",
"label": "Postgres password [e.g. mealie]"
},
"POSTGRES_DB": {
"description": "Must match the database name set in mealie-db.",
"label": "Database name [e.g. mealie]"
}
}
}
},
"container_links": {
"mealie-app": [
{
"name": "MealieAppToDB",
"source_container": "mealie-db"
}
]
}
}
}
If you want to play with it to see whether that works for you, follow the contribution guideline with creating the directory rockons-metastore in the appropriate place.
If you like it/it works for you, open a request (even with the minimal information you mentioned above) and I will submit it as a pull request. That way we have full attribution.
It works perfectly fine. I am amazed and so thankful! It just needs some tooltips and infos on the setup interface, in my opinion and it will be perfect!!
Thanks again!