Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 12 00:31
    dependabot[bot] labeled #212
  • May 12 00:31
    dependabot[bot] opened #212
  • May 12 00:31

    dependabot[bot] on npm_and_yarn

    Bump codemirror from 5.41.0 to … (compare)

  • May 09 11:40
    dependabot[bot] labeled #211
  • May 09 11:40
    dependabot[bot] opened #211
  • May 09 11:40

    dependabot[bot] on npm_and_yarn

    Bump hosted-git-info from 2.7.1… (compare)

  • May 07 00:26

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 07 00:26
    dependabot[bot] closed #200
  • May 07 00:26
    dependabot[bot] commented #200
  • May 07 00:26
    dependabot[bot] labeled #210
  • May 07 00:26
    dependabot[bot] opened #210
  • May 07 00:26

    dependabot[bot] on npm_and_yarn

    Bump lodash from 4.17.4 to 4.17… (compare)

  • May 06 22:38

    dependabot[bot] on npm_and_yarn

    (compare)

  • May 06 22:38
    dependabot[bot] closed #202
  • May 06 22:38
    dependabot[bot] commented #202
  • May 06 22:38
    dependabot[bot] labeled #209
  • May 06 22:38
    dependabot[bot] opened #209
  • May 06 22:38

    dependabot[bot] on npm_and_yarn

    Bump handlebars from 4.0.12 to … (compare)

  • May 06 18:44
    dependabot[bot] labeled #208
  • May 06 18:44
    dependabot[bot] opened #208
daleewald
@daleewald
Then, when trying to create a non-admin user, I get "this.context doesn't exist" error in the UI
Alex Arriaga
@alex-arriaga
Did you install Carbon in your localhost or in FQDN?
Wait... which version of the docs are you reading?
It should be 1.0.x :)
daleewald
@daleewald
I installed carbon on a remote host (VM); set host mapping for that vm on my laptop, then address the workbench by the mapped fqdn
Alex Arriaga
@alex-arriaga
Could you paste your config.yaml file, please?
daleewald
@daleewald
I installed the alpha version; docs are the alpha
Basically copied the config.yaml from docs
Should the host: value match my FQDN?
Alex Arriaga
@alex-arriaga
In the config.yaml that is in the docs, the host is set to localhost; I think it should be changed to your FQDN
Yep
daleewald
@daleewald
ok, do I need to rm the container and re-create; or just stop/start?
Alex Arriaga
@alex-arriaga
I would say remove it
That was the same mistake I made ;)
And then just by removing the container, changing my config.yaml and re-runing the container worked
daleewald
@daleewald
Just workbench container or both?
Alex Arriaga
@alex-arriaga
The platform
carbonld-platform container
daleewald
@daleewald
Did you have to purge the data directory?
Alex Arriaga
@alex-arriaga
I removed it too, just to have a clean install; not sure if that was needed
daleewald
@daleewald
Thanks @alex-arriaga the platform message is resolved
Alex Arriaga
@alex-arriaga
Cool :thumbsup:
daleewald
@daleewald
But: still when creating non-admin user I get "this.context is undefined" trying to submit. And I see there is no network request attempt (no submit).
Alex Arriaga
@alex-arriaga
As far as I know, this alpha version doesn’t have security/auth implemented yet...
Miguel Aragón
@MiguelAraCo
Wait, how are you creating a non-admin user?
Are you sure you are running the alpha version of the workbench?
daleewald
@daleewald
Yes, I used:
docker run -d --name carbonldp-workbench -p 8000:80 -e "CARBON_HOST=carbon2.local.com:8083" -e "CARBON_PROTOCOL=http" carbonldp/carbonldp-workbench:1.0.x-alpha
By non-admin user I meant: at the login screen, "Don't have an account? <create one now>"
Alex Arriaga
@alex-arriaga
mmm, in my case I didn’t need that “admin user”, when I opened the workbench in 8000 port, it went directly to this UI
w.png
daleewald
@daleewald
Yes, same here. OK we were blending the two versions of the documentation. I see there is no additional user in the newer documentation
Miguel Aragón
@MiguelAraCo
Oh, ok. That explains it :+1:
Alex Arriaga
@alex-arriaga
jeje
daleewald
@daleewald
Yes. Wipe this conversation from memory :smile:
Miguel Aragón
@MiguelAraCo
We noticed that, in the documentation, the active version number isn't as clear as it could be
We created an issue to work on it :smile:
Juan Flores
@thechosenjuan
I think this has been discussed already, but I'm having problems connecting the workbench to the platform
Screen Shot 2018-01-22 at 6.26.23 PM.png
I'm running my instance in localhost
any advise is welcome
Miguel Aragón
@MiguelAraCo
localhost:8083?
The workbench was able to connect to the platform
The message you got is a known bug
But the number of documents/triples is being displayed so everything seems to be fine in your side
A hard refresh on that page should get rid of that message
Juan Flores
@thechosenjuan
yes, that did it
thanks!
will a hard reset be necessary to load the workbench correctly everytime?
Miguel Aragón
@MiguelAraCo
No