425 karma · joined February 22, 2012
I am working on https://github.com/daptin/daptin
https://github.com/daptin/daptin
A JSON config plus backing database (mysql/postgres/sqlite) defines your complete environment.
[1] https://spacy.io/models/en [2] https://github.com/huggingface/neuralcoref/tree/bee05b1b55e3...
Also that issue is in my code (poor naming choice). Will put up the code on github soon. Hope that will help.
This current docker image is not exposing those other languages but I can expose them in an update if it helps a lot of people.
[1] https://spacy.io/usage/models [2] http://compling.hss.ntu.edu.sg/omw/
Added GPU would probably help both spacy and neuralcoref in performance.
> Also, it would be useful to see the Dockerfile or script that generated this img.
Will put it on github shortly.
Remote: Yes, remote only
Willing to relocate: Maybe
Technologies: golang, java, python, server side programming, client js, nodejs, database design, mysql/postgres, kubernetes, ci/cd, architecture, testing, benchmarking, vuejs, angular
Résumé/CV: https://www.linkedin.com/in/parth-mudgal-8129604a/
Email: artpar [at] gmail.com
I love writing code, looking to helping out teams and startups.
ps: i work for this
Daptin works with JSONs and converts JSONs to live websites. Docs are here [2]
[1] https://github.com/daptin/daptin [2] http://docs.dapt.in
Two parts:
- Storage
Daptin connects to a storage (eg google drive) using rclone, we upload a zip which goes to gdrive. That was how the site is stored.
- Serve
Another part of daptin is "sub site", where we say "serve this storage folder" under this sub-domain/sub-path
GrapeJS is injected to the page if editor permission is given to current user. Changes by GrapeJS will reflect back to original storage (thanks to rclone)
Now that allows us to make static sites. But daptin already is exposing JSON apis for all your data. So along with those built in "Static drag and drop components", New "dynamic" components, which will act as "templates" for the data coming in via json api.
Plus we also have actions, which take in inputs like form submission, so the form inputs can be pointed to those actions.
Will write a longer article soon along with gifs.
http://docs.dapt.in/state_tracking/
Would love feedback.
Current System ===
- End to end flow of the system (what is the first point of contact to your server for a HTTP request)
- How is the architecture laid out (services talking to each other)
- What are the front-facing services
- What are the back services (crons/queue consumers)
- How are the domains managed, how are all the domains setup
- How is the deployment setup for across services
- What are the background activities they were silently taking care of (manual crons)
- What system is responsible for which business activity
- What are all the 3rd party services your system talks to
Future System ===
- What are the current parts of the system they were actively working on
- How were these new services going to fit in the current architecture
- Were they planning of refactoring some parts/services
- Were they planning of rewriting any part of code
You can check it out here: https://github.com/artpar/daptin
The build scripts are located here: https://github.com/daptin/daptin/tree/master/scripts
The current setup is recognised by travis and semaphoreci.
Does that number ever increase ?