Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 19 21:34

    mhernandeza on master

    Update issue templates (compare)

  • Jun 19 21:05

    mhernandeza on master

    Update issue templates (compare)

  • Jun 19 20:24
    maggsmg closed #2
  • Jun 19 20:22

    maggsmg on master

    Update README.md (compare)

  • Jun 19 16:48
    MiguelAraCo edited as member
  • Jun 19 16:40
    MiguelAraCo added as member
  • Jun 19 16:37
    Frost-bit removed as member
  • Jun 19 16:29
    Frost-bit added as member
  • Dec 01 2018 01:22

    MiguelAraCo on master

    Delete file left by GitBook (compare)

  • Dec 01 2018 01:20
    MiguelAraCo deleted #7
  • Dec 01 2018 01:20
    MiguelAraCo closed #8
  • Dec 01 2018 01:20
    MiguelAraCo commented #8
  • Dec 01 2018 01:19
    MiguelAraCo closed #9
  • Dec 01 2018 01:19
    MiguelAraCo closed #10
  • Dec 01 2018 01:18
    MiguelAraCo closed #11
  • Dec 01 2018 01:18
    MiguelAraCo commented #11
  • Dec 01 2018 01:16
    MiguelAraCo closed #12
  • Dec 01 2018 01:16
    MiguelAraCo commented #12
  • Dec 01 2018 01:14
    MiguelAraCo transferred #15
  • Nov 30 2018 23:01
    Yahaire commented #15
Miguel Aragón
@MiguelAraCo
(Although it doesn't explicitly say that... maybe we should create a FAQ section)
The only thing that you need to be worried about, is if you want your objects to be documents on their own, or be fragments of another document. Which is covered in the page "Object model"
Miguel Aragón
@MiguelAraCo
You have a lot of options:
  • Store post's comments as descendants of the post via an AccessPoint. Meaning comments will end up having IDs like: posts/my-post/comments/123123/
  • Store post's comments as children of a document that will hold all of the sites comments. After that, link the comment to its post. Meaning comments/123123/
  • Store post's comments as fragments of the post. Meaning _:123123 inside posts/my-post/
  • Store post's comments as named fragments of the post. Meaning posts/my-post/#comment-12312
Which one is the best? Depends on the situation and your particular requirements
(Don't get me wrong, I think we need to state this somewhere in the documentation, I'm just writing it here for now)
AlexSerrano22
@AlexSerrano22
hi again :P
CarbonLDP/carbonldp-platform#8

and a comment about the documentation of creating an access point on the tab "JavaScript ES2015", you have this lines:

        return project.refresh<Project>();
        return person1.refresh<Person>();

but the classes are on "typescript" only :P

Miguel Aragón
@MiguelAraCo
Please help us by creating issues for any typo or mistake in the documentation, in the https://github.com/CarbonLDP/carbonldp-website repository
AlexSerrano22
@AlexSerrano22
ok
Miguel Aragón
@MiguelAraCo
Thank you for reporting them :smile:
AlexSerrano22
@AlexSerrano22
CarbonLDP/carbonldp-website#194
Miguel Aragón
@MiguelAraCo
:clap:
Alex Arriaga
@alex-arriaga
Perfect @MiguelAraCo
Cody Burleson
@codyburleson
Perfect? Hmmm... I wouldn't go that far. ;-)
Alex Arriaga
@alex-arriaga
:D
Miguel Aragón
@MiguelAraCo
Just published a new version of the platform: 1.0.0-alpha.8. The docker image 1.0.x-alpha now points to that version as well. It includes a somewhat critical bug so we advise you to update your instances if you are using the alpha line.
AlexSerrano22
@AlexSerrano22
thanks
Alex Arriaga
@alex-arriaga
Hi good morning, I am stargint to test the real time capabilities of Carbon, I haven’t worked with rabbitmq yet. In your opinion is that the best option of a message broker to be connected with Carbon?
Miguel Aragón
@MiguelAraCo
For now it is the only one we have tested integration with
So it is the one we recommend right now
Alex Arriaga
@alex-arriaga
Ok, I will install it then
Alex Arriaga
@alex-arriaga
If I change the port or the host for my messaging broker in the config.yaml file, should I destroy the container and re-run it?
Miguel Aragón
@MiguelAraCo
You shouldn't need to do that
Alex Arriaga
@alex-arriaga
I see the requests to the /broker endpoint, but my Rabbit seems not to be connected to Carbon
Screen Shot 2018-01-25 at 12.15.00 PM.png
Screen Shot 2018-01-25 at 12.47.16 PM.png
Miguel Aragón
@MiguelAraCo
How are you installing RabbitMQ?
Alex Arriaga
@alex-arriaga
I have an Ubuntu host, I installed it using a regular .deb package
# Running this command gives me
epmd -names

epmd: up and running on port 4369 with data:
name rabbit at port 25672
In my config.yaml I have:
messaging:
  broker:
    host: carbonldp.webtraining.zone
    port: 25672
Miguel Aragón
@MiguelAraCo
You need to enable RabbitMQ's STOMP plugin
And configure Carbon to connect to the STOMP port (normally 61613)
Our documentation is still lacking a proper guide on how to setup this but we are working on it
Alex Arriaga
@alex-arriaga
Hi guys, I decided to create an issue in github regarding my real time error CarbonLDP/carbonldp-js-sdk#214
Alex Arriaga
@alex-arriaga
Hello there
We created an application few months ago, we destroyed our development server but we saved our “data” folder. Is there any docs about how to restore this data into a brand new Carbon instance (localhost)?
We tried to paste our “data” folder directly replacing the existing folder in our localhost, but it didn’t work.
Miguel Aragón
@MiguelAraCo
You should be able to do that
Just make sure that the server is down when you do it
The server should automatically upgrade your data to the new model it is using
Unfortunately we haven't thoroughly tested this as there's a lot of different combinations to test
If that doesn't work, please send us your data and we'll help you from there
Context: I request it because as I understand this data isn't sensitive. The application was part of an internal hackaton. In external cases our support would be different.
Alex Arriaga
@alex-arriaga
Just tried again, but I am not seeing my data… :shipit:
Miguel Aragón
@MiguelAraCo
What command are you using to run your platform?
And also, are you using a configuration file called config.yaml?
Miguel Aragón
@MiguelAraCo

We are happy to announce that a new major version has been released in our product lineup:

v5.0.0

Main new features:

  • Support for external repositories (Stardog and remote RDF4J repositories like Graph DB)
  • Data change events (listen to the creation, deletion or modification of documents)
  • Document querying (query documents without leaving the document-based model)

Plus a lot of bugfixes and performance improvements

If you want to know more head over to carbonldp.com or subscribe to our newsletter to receive the release announcement