Dear, I've forwarded your request to the second level support.

Best,
Daniele

Hi Daniele,

thanks for reporting your problem. We have updated the docker images to provide a new command: createsuperuser. We have also updated the documentation, but for reference, you can create a superuser by running the following command:

$ docker-compose run --rm wirecloud createsuperuser

Best regards,
Álvaro

Dear Daniele,

were you able to create the admin user?

Best regards,
Álvaro

Dear Alvaro, I'm not the reporter of the issue. I've just forwarded it.

Let me send a request to the original reporter (nagin@il.ibm.com)

The issue has been emailed:

• Time sent: 04/Jul/16 11:38 AM
• To: nagin@il.ibm.com
• with subject: *(HELP-6827) [Fiware-lab-help] FIWARE Lab Assistance *
  

Dear,

Can you please provide feedback on the resolution proposed by Alvaro ?

Daniele

Closing due inactivity

Alvaro:
Thanks and sorry I did not get back to you sooner. I get so much FIWARE mail that it must have deleted your response since I did not think it was related to me.
I followed the instruction on the DockerHub and it worked! I even did your tutorial. It looks good but I got a bit confusing on the wiring (I will try again another time). But the main things is that it works, so congratulations.

There are a few glitches that you should know about:

• 1st a small point: Your docker-compose.yml uses the latest tag in two places. Apparently, docker-compose does not automatically pull from dockerhub the latest unless you do an explicit pull. I suggest adding something to the documentation so the people get the actual latest
• I do not think that you want to expose the host port for postgres's 5432. I think you expect the external interaction through the Wirecloud guide. If I am correct then you should simply expose the port internally, i,e. use expose instend of port in the docker-compose.yml. I tried it out and it works fine.
• data is always in Restarting state. This looks suspicious to the user so it is probably best document that it is not a problem.
• You seem to be getting parsing errors. Here is the output:
  nagin@rcc-hrl-kvg-558:~/compose_test/wirecloud$ sudo docker-compose run --rm wirecloud initdb
  System check identified some issues:

WARNINGS:
?: (urls.W002) Your URL pattern '^/(?P<protocol>[^/])/(?P<domain>[^/])(?P<path>|/.*)$' [name='wirecloud|proxy'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/media/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)/(?P<file_path>.*)' [name='wirecloud_catalogue.media'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])$' [name='wirecloud_catalogue.resource_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])$' [name='wirecloud_catalogue.resource_versions_collection'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)$' [name='wirecloud_catalogue.resource_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)/changelog$' [name='wirecloud_catalogue.resource_changelog_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)/userguide$' [name='wirecloud_catalogue.resource_userguide_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resources$' [name='wirecloud_catalogue.resource_collection'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resources/suggest$' [name='wirecloud_catalogue.resource_suggestion'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/versions' [name='wirecloud_catalogue.resource_versions'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
Operations to perform:
Apply all migrations: oauth2provider, sessions, admin, contenttypes, auth, platform, catalogue
Running migrations:
Rendering model states... DONE
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying catalogue.0001_initial... OK
Applying oauth2provider.0001_initial... OK
Applying platform.0001_initial... OK
Applying platform.0002_auto_20160127_1143... OK
Applying sessions.0001_initial... OK
nagin@rcc-hrl-kvg-558:~/compose_test/wirecloud$
nagin@rcc-hrl-kvg-558:~/compose_test/wirecloud$ sudo docker-compose run --rm wirecloud createsuperuser
System check identified some issues:

WARNINGS:
?: (urls.W002) Your URL pattern '^/(?P<protocol>[^/])/(?P<domain>[^/])(?P<path>|/.*)$' [name='wirecloud|proxy'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/media/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)/(?P<file_path>.*)' [name='wirecloud_catalogue.media'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])$' [name='wirecloud_catalogue.resource_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])$' [name='wirecloud_catalogue.resource_versions_collection'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)$' [name='wirecloud_catalogue.resource_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)/changelog$' [name='wirecloud_catalogue.resource_changelog_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resource/(?P<vendor>[^/])/(?P<name>[^/])/(?P<version>[^/]+)/userguide$' [name='wirecloud_catalogue.resource_userguide_entry'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resources$' [name='wirecloud_catalogue.resource_collection'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/resources/suggest$' [name='wirecloud_catalogue.resource_suggestion'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
?: (urls.W002) Your URL pattern '^/versions' [name='wirecloud_catalogue.resource_versions'] has a regex beginning with a '/'. Remove this slash as it is unnecessary.
Username (leave blank to use 'root'): admin
Email address: nagin@il.ibm.com
Password:
Password (again):
Superuser created successfully.
— Finally, I think you should monitor the dockerhub comment for wirecloud. My original questions were posted there but you never responded.

I hope this feedback is helpful.

Ken

Thanks and sorry I did not get back to you sooner. I get so much FIWARE mail that it must have deleted your response since I did not think it was related to me.

Don't worry , thank you for taking your time and reporting those problems

I followed the instruction on the DockerHub and it worked! I even did your tutorial. It looks good but I got a bit confusing on the wiring (I will try again another time). But the main things is that it works, so congratulations.

Great . About the tutorial, what tutorial did you followed? the one available on the Read the Docs page?, or the "Basic concepts" interactive tutorial available directly on WireCloud?

There are a few glitches that you should know about:

• 1st a small point: Your docker-compose.yml uses the latest tag in two places. Apparently, docker-compose does not automatically pull from dockerhub the latest unless you do an explicit pull. I suggest adding something to the documentation so the people get the actual latest
• I do not think that you want to expose the host port for postgres's 5432. I think you expect the external interaction through the Wirecloud guide. If I am correct then you should simply expose the port internally, i,e. use expose instend of port in the docker-compose.yml. I tried it out and it works fine.
• data is always in Restarting state. This looks suspicious to the user so it is probably best document that it is not a problem.

Ok. Would you mind creating a pull request with the proposed changes? We are busy finishing other tasks and vacations are near so we are not going to be able to tackle this until returning from vacations .

You can find the documentation on github (in case you finally want to create the pull request ): https://github.com/Wirecloud/docker-wirecloud/blob/master/README.md

• You seem to be getting parsing errors. Here is the output:
  ...

working on solving it

• Finally, I think you should monitor the dockerhub comment for wirecloud. My original questions were posted there but you never responded.

It's a pity, but docker hub don't send notifications about user activity (e.g new comments), moreover comments are at the bottom of the page, etc... So, we try to monitor it, but is not easy . In fact, I answered you in docker hub before answering you here . We have added a "User Feedback" section recommending to use other (more agile) channels for the feedback.

I hope this feedback is helpful.

Ken

For sure, your feedback is very useful. Thanks