superset/.gitignore

51 lines
551 B
Plaintext
Raw Normal View History

2015-07-06 18:18:51 -04:00
*.pyc
2016-11-17 13:05:08 -05:00
yarn-error.log
_modules
superset/assets/coverage/*
2016-04-14 02:07:25 -04:00
changelog.sh
2015-09-23 17:33:44 -04:00
.DS_Store
2015-09-25 18:43:50 -04:00
.coverage
2015-12-17 19:26:36 -05:00
_build
_static
2016-04-07 02:32:35 -04:00
_images
_modules
superset/bin/supersetc
2016-03-29 11:40:18 -04:00
env_py3
envpy3
2016-03-29 11:40:18 -04:00
.eggs
2015-09-11 18:32:42 -04:00
build
2015-07-16 20:55:36 -04:00
*.db
2015-07-15 13:12:32 -04:00
tmp
superset_config.py
2015-07-21 16:54:31 -04:00
local_config.py
2015-09-05 12:23:46 -04:00
env
2015-09-05 18:08:38 -04:00
dist
superset.egg-info/
2015-07-23 02:17:51 -04:00
app.db
*.bak
.idea
*.sqllite
.vscode
.python-version
.tox
2018-03-06 02:11:40 -05:00
dump.rdb
# Node.js, webpack artifacts
*.entry.js
*.js.map
node_modules
npm-debug.log*
superset/assets/version_info.json
2017-09-12 12:04:48 -04:00
# IntelliJ
*.iml
venv
@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