gdev icon indicating copy to clipboard operation
gdev copied to clipboard

Helper script for developing containerized web applications.

Results 24 gdev issues
Sort by recently updated
recently updated
newest added

# This is for production docker image FROM devgeniem/wordpress-server:php7.0 # Use port 8080 for flynn/router # Use these uid/gid in production by default and these can be changed when needed...

Not sure what happens, as the files appear in the correct place if inspected with `gdev shell`, but for some reason media images are broken at least under wp-admin if...

Running command on terminal prints an error "the input device is not a TTY" ``` $ flynn -c production -a project run wp db export - | gdev exec wp...

Using this: https://github.com/devgeniem/wp-project/blob/master/docker-compose.yml Getting this: web_1 | [services.d] started php-fpm web_1 | [16-Nov-2016 11:59:20] ERROR: [pool www] the chdir path '/var/www/project/web' does not exist or is not a directory web_1...

`Contacting server... Connected [//5335fb0e62f6//var/www/project -> //dev-machine//Users/user/Work/Pipeline/projecta] Looking for changes Fatal error: Server: End_of_file exception raised in loading archive (this indicates a bug!) INFO: Sync is ready!` I.e. the sync ain't...

bug

Find a way to run webpack watch from outside the frontend container. Something like: ``` gdev run frontend "cd {dir_where_the_webpack_config_exists}; ./node_modules/webpack/bin/webpack.js --watch;" ```

When installing node modules within the frontend container, the packages are assigned to root user instead of the wordpress user.

After installing node modules within the front container and running webpack, the sync fails due to permission issues. Docker version 1.12.1, build 6f9534c `````` Looking for changes Waiting for changes...

bug

ATM it just tries with empty port and fails ``` $ gdev sync INFO: Starting to sync into port: ... Contacting server... Fatal error: ill-formed root specification socket://localhost:/ INFO: Sync...

fatal: [127.0.0.1]: FAILED! => {"failed": true, "msg": "timeout waiting for privilege escalation password prompt:\n\nWARNING: Improper use of the sudo command could lead to data loss\nor the deletion of important system...