-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while trying to run the platform locally #6
Comments
I have the same problem when running
|
Hi @agarciadom you can use the following docker-compose file. version: '3.8'
services:
mongo:
image: mongo
container_name: mongo
ports:
- 27017:27017
volumes:
- ./database/db:/data/db
- ./database/dev.archive:/Databases/dev.archive
- ./database/production:/Databases/production
restart: always
mongo-express:
image: mongo-express
container_name: mexpress
environment:
- ME_CONFIG_BASICAUTH_USERNAME=admin
- ME_CONFIG_BASICAUTH_PASSWORD=admin
links:
- mongo
ports:
- 8081:8081
restart: always
collaborative:
image: giordanotin/collaborative:1.2
container_name: collaborative
links:
- mongo
ports:
- 5001:5001
restart: always
persistance:
image: giordanotin/persistance:1.6
container_name: persistance
links:
- mongo
ports:
- 5002:5002
restart: always
memorec:
container_name: memorec
image: giordanotin/memorec:1.8
ports:
- 8080:8080
restart: always
frontend:
image: giordanotin/jjodel:latest
container_name: frontend
depends_on:
- memorec
- collaborative
- persistance
ports:
- 80:80
restart: always Please let me know if it works. |
That worked, thank you! I had to go to http://localhost instead of http://localhost:3000 as in the README, though, and I also had to create my own account. Is that to be expected? Is there a default username/password that I could use without registering? |
Hi Antonio,
Perfect. Happy to hear that. If you need any details and tutorials on how to model in jjodel, we are more than happy to help you.
You are right; the port is incorrect. We are restructuring the repository and updating the deployment guide.
You can access jjodel in offline mode (the link is below the login page), which does not require any registration. In offline mode, you cannot use the collaborative features, and all data are stored in the client’s local storage.
I’m wondering if we can integrate the EPSILON playground into jjodel (at least to support model transformation). Internally, jjodel has its representation as well as JOL, an operational language (a kind of EOL).
However, jjodel models (and metamodels) are compatible with the EMF format, and we can export models (and metamodels) in standard XMI.
I suppose the ESPILON playground web tool has REST APIs behind it. Do you have any guidelines or examples to check the feasibility? What do you think?
Additionally, the EPSILON playground includes a web-based editor for different EPSILON languages. Can we integrate them into jjodel?
We are open to any collaborations, and your suggestions are welcome.
Cheers,
Juri
Da: Antonio García-Domínguez ***@***.***>
Data: mercoledì, 6 novembre 2024 alle ore 20:34
A: MDEGroup/jjodel ***@***.***>
Cc: Juri Di Rocco ***@***.***>, Comment ***@***.***>
Oggetto: Re: [MDEGroup/jjodel] Error while trying to run the platform locally (Issue #6)
That worked, thank you! I had to go to http://localhost instead of http://localhost:3000 as in the README, though, and I also had to create my own account. Is that to be expected? Is there a default username/password that I could use without registering?
—
Reply to this email directly, view it on GitHub<#6 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABXTOHPQWAC6I5CNCXRU443Z7JVLNAVCNFSM6AAAAABOUKDLL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQGYYTCOBWGI>.
You are receiving this because you commented.Message ID: ***@***.***>
|
While trying to run the platform locally today, I ran into this error message while trying to run the platform from my Apple Silicon Mac:
You can try to reproduce this issue with these commands, from a clean clone:
I have also tried to run this locally, by installing Node directly, using the same basic
npm install
andnpm run start
commands, and I end up with the same error message.The text was updated successfully, but these errors were encountered: