Cloudron build mess up

[jimcavoli]

You can edit/remove the information in $HOME/.cloudron.json that deals with that folder on your machine to correct the repository info or just delete the block to make the CLI re-prompt you on the next run.

[scooke]

@jimcavoli Great, I found it, it was just named .cloudron.

What is the proper response for

Enter repository (e.g registry/username/org.omekas.cloudronapp):

Is this my own repository of the cloned app? Or is it not the repository of the creaters, like so - registry/lenef/omeka-s-app? Is it registry/myusernameoncloudron/omeka-s-app or my local user like registry/melocally/omeka-s-app Or is it yet some other repository that I have to create??

[robi]

it's either the public docker registry service, or the new self-hosted one in the app store called docker registry.

[scooke]

@robi I understand the words, but not the meaning!

Seeing as this is a new repository from these kind people, I don't think they have it listed" (is that the right word?) in the public docker registry service (and I'm not even sure what that is, and what the url would be for it). Same thing for the "new self-hosted one in the app store called docker registry". It is new, I just cloned it, so as far as I know there is no repository in the app store repository ... ok, I followed a few links and found https://git.cloudron.io/cloudron/omeka-s-app, so this is the repository I need, right? The portion I enter is just cloudron/omeka-s-app? or does the "registry" in the Enter repository (e.g registry/username/org.omekas.cloudronapp) refer to https://git.cloudron.io?

[robi]

@scooke repository != registry.

repo = github repo where you found the code

reg = a docker image repo where the build scripts can place the built image, so that docker can pull it down and install it.

[msbt]

@scooke the registry refers to a docker registry where you push the image after building it, so it should be either a docker.io registry or you can use the new registry-app from cloudron. I've made a post here that you can follow.

[kallados]

@scooke I think i get the same problem. Im really not sure about the Name

Enter repository (e.g registry/username/org.omekas.cloudronapp)

[nebulon]

Oh I see the confusion. So indeed what the cli tool asks for here is the docker image registry repository. Not the git repository.
I guess we can just remove "repository" here from the cli tool output to avoid that confusion.

To clarify an example setting for this for example for the omeka image pushed to the appstore by the Cloudron team: docker.io/cloudron/org.omekas.cloudronapp this has to be set to whatver your docker hub account is, or if another docker registry is used, also the docker.io has to change to your registry domain.

[kallados]

@nebulon Sry for maybe stupid Question.. but

docker.io/cloudron/org.omekas.cloudronapp

"cloudron" should to be replaced with my username right? Or is this pointed to chown cloudron:cloudron? Thanks

[nebulon]

@kallados indeed it has to be adjusted to your own account name. cloudron here refers to our account at the docker hub. The chown is for the unix user named cloudron on your system. Nothing to do with the docker hub registry service.