2018-09-14 18:38:14 -04:00
|
|
|
*.bak
|
|
|
|
|
*.db
|
2015-07-06 18:18:51 -04:00
|
|
|
*.pyc
|
2018-09-14 18:38:14 -04:00
|
|
|
*.sqllite
|
2018-08-21 16:45:42 -04:00
|
|
|
*.swp
|
2015-09-25 18:43:50 -04:00
|
|
|
.coverage
|
2018-09-14 18:38:14 -04:00
|
|
|
.DS_Store
|
|
|
|
|
.eggs
|
|
|
|
|
.idea
|
|
|
|
|
.python-version
|
|
|
|
|
.tox
|
|
|
|
|
.vscode
|
2015-12-17 19:26:36 -05:00
|
|
|
_build
|
2016-04-07 02:32:35 -04:00
|
|
|
_images
|
2016-11-17 14:58:33 -05:00
|
|
|
_modules
|
2018-09-14 18:38:14 -04:00
|
|
|
_static
|
|
|
|
|
build
|
|
|
|
|
app.db
|
|
|
|
|
changelog.sh
|
|
|
|
|
dist
|
|
|
|
|
dump.rdb
|
|
|
|
|
env
|
2016-03-29 11:40:18 -04:00
|
|
|
env_py3
|
2018-05-07 18:26:19 -04:00
|
|
|
envpy3
|
2015-07-21 16:54:31 -04:00
|
|
|
local_config.py
|
2018-09-14 18:38:14 -04:00
|
|
|
superset_config.py
|
2016-11-10 02:08:22 -05:00
|
|
|
superset.egg-info/
|
2018-09-14 18:38:14 -04:00
|
|
|
superset/bin/supersetc
|
|
|
|
|
tmp
|
2016-02-19 14:39:50 -05:00
|
|
|
|
|
|
|
|
# Node.js, webpack artifacts
|
|
|
|
|
*.entry.js
|
|
|
|
|
*.js.map
|
|
|
|
|
node_modules
|
2018-02-07 11:12:45 -05:00
|
|
|
npm-debug.log*
|
2018-09-14 18:38:14 -04:00
|
|
|
superset/assets/coverage/*
|
|
|
|
|
superset/assets/cypress/screenshots
|
|
|
|
|
superset/assets/cypress/videos
|
2017-01-12 15:32:06 -05:00
|
|
|
superset/assets/version_info.json
|
2018-09-14 18:38:14 -04:00
|
|
|
yarn-error.log
|
2017-06-07 02:44:57 -04:00
|
|
|
|
2017-09-12 12:04:48 -04:00
|
|
|
# IntelliJ
|
|
|
|
|
*.iml
|
2018-02-20 20:07:16 -05:00
|
|
|
venv
|
2018-03-12 00:54:49 -04:00
|
|
|
@eaDir/
|
Init docker for local development environment. (#4193)
This commit will try to dockerize superset in local development
environment.
The basic design is:
- Enable superset, redis and postgres service instead of using sqlite,
just want to simulate production environment settings
- Use environment variables to config various app settings. It's easy to
run and config superset to any environment if we use environment than
traditional config files
- For local development environment, we just expose postgres and redis
to local host machine thus you can connect local port via `psql` or
`redis-cli`
- Wrap start up command in a standard `docker-entrypoint.sh`, and use
`tail -f /dev/null` combined with manually `superset runserver -d` to
make sure that code error didn't cause the container to fail.
- Use volumes to share code between host and container, thus you can use
your favourite tools to modify code and your code will run in
containerized environment
- Use volumes to persistent postgres and redis data, and also
`node_modules` data.
- If we don't cache `node_modules` in docker volume, then every time
run docker build, the `node_modules` directory, will is about 500 MB
large, will be sent to docker daemon, and make the build quite slow.
- Wrap initialization commands to a single script `docker-init.sh`
After this dockerize setup, any developers who want to contribute to
superset, just follow three easy steps:
```
git clone https://github.com/apache/incubator-superset/
cd incubator-superset
cp contrib/docker/{docker-build.sh,docker-compose.yml,docker-entrypoint.sh,docker-init.sh,Dockerfile} .
cp contrib/docker/superset_config.py superset/
bash -x docker-build.sh
docker-compose up -d
docker-compose exec superset bash
bash docker-init.sh
```
2018-06-10 00:26:41 -04:00
|
|
|
|
|
|
|
|
# docker
|
|
|
|
|
/Dockerfile
|
|
|
|
|
/docker-build.sh
|
|
|
|
|
/docker-compose.yml
|
|
|
|
|
/docker-entrypoint.sh
|
|
|
|
|
/docker-init.sh
|
