AlexiCauvin 5b61eecd2d add tinymce in asset | 6 년 전 | |
---|---|---|
dist | 6 년 전 | |
jsonserver | 6 년 전 | |
src | 6 년 전 | |
.editorconfig | 7 년 전 | |
.gitignore | 6 년 전 | |
README.md | 6 년 전 | |
package.json | 6 년 전 | |
webpack.config.js | 6 년 전 |
This project is the frontend part of Tracim.
Install all dependencies
$ npm install
Build the sources
$ npm run build
Load dist/index.html
in your webserver.
Install all dependencies
$ npm install
Start development server (webpack dev server)
$ npm run servdev
Alternatively, you can use $ npm run servdev-dashboard
to use webpack-dashboard to have a better server interface.
Start mockapi server
$ npm run mockapi
Tracim is a skeleton that rely on apps to do stuffs. (like to manage Documents, Files, Threads ...)
Apps all are independant React applications and have their own repositories and can be freely added or removed from Tracim without the needs for a rebuild.
Apps acts like plugins.
You need to separately get the built version of each apps and add them to dist/app
folder. Apps file names should be of the form of 'appName.app.js'.
To do that 1) go to each Apps repositories ; currently 2 : (more to come)
npm install && npm run build
3) copy the appRepository/dist/appName.app.js file generated and past it to tracim_frontend/dist/app folderBy default, for development, tracim_frontend expects every apps but wont crash if one is missing (currenlt not all of them are exists anyway)
Apps are independents React application so you can test them out on their own.
/!\ Documentation on Apps interface is work in progress. /!
To test them inside Tracim, you need to build them and copast them to tracim_frontend/dist/app.
You also need to make the mock api able to tell tracim_frontend that it handle you app :
app_config
propertyGLOBAL_renderApp
. All of this will be handled by backend later on, this is all work in progress stuffs.