voxpupuli / crafty

CRAFTY - Containerized Resources And Funky Tools (in) YAML
GNU Affero General Public License v3.0
15 stars 8 forks source link

Renaming images or adding a shorter name? #61

Closed rwaffen closed 4 months ago

rwaffen commented 5 months ago

Discussed in https://github.com/voxpupuli/crafty/discussions/42

Originally posted by **rwaffen** April 4, 2024 initially I named the git repo container-puppetserver / container-puppetdb. this was to make sure it is not confused with the real git projects from puppet and make sure you can see that this only is for container builds. but so also the package/container image itself is called that way. but recently i found out, that this has not to be like that. the image name now `voxpupuli/container-puppetserver:latest` shot name: `voxpupuli/puppetserver:latest` so we could build a package only called puppetserver and add it to the registry. the question is now: do we want to do this? do we want to rename it or add a second package/image with the short name? or do we just keep the names now? any suggestions?

as discussed we can use the shorter names

bastelfreak commented 5 months ago

I think a second name is fine. Renaming can always result in strange errors and I don't think the old name is too bad.

tuxmea commented 5 months ago

I would recommend to keep the long name and add the short name. Next we can make an announcement, that we switch names and can afterwards remove the long names. This will give users the option to migrate over time.

my 5pc.

rwaffen commented 5 months ago

okay, will keep the old names and only add the new. issues was a bit unclear from wording, just created it from discussion.