Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
# Backup | |
docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql | |
# Restore | |
cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE | |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
#!/bin/bash | |
# pre-push hook to enable/disable travis and github actions push builds | |
# based on the nature of the pushed branches. | |
# - upstream and deleted ones won't be built. | |
# - development ones will be built. | |
# Requires travis (client) gem binary installed. | |
# Requires gh (client) binary installed. | |
# Useful for people wanting to keep their upstream branches updated, | |
# and not causing them to perform travis/github actions builds all the time, like me :-) | |
IFS=' ' |
@Configuration | |
@EnableJpaAuditing(dateTimeProviderRef = "dateTimeProvider") | |
@EnableJpaRepositories("com.sample.repository") | |
@EnableTransactionManagement | |
public class DatabaseConfiguration implements EnvironmentAware { | |
private final Logger log = LoggerFactory.getLogger(DatabaseConfiguration.class); | |
private RelaxedPropertyResolver dataSourcePropertyResolver; | |
private RelaxedPropertyResolver slaveDataSourcePropertyResolver; |
This is how to connect to another host with your docker client, without modifying your local Docker installation or when you don't have a local Docker installation.
First be sure to enable the Docker Remote API on the remote host.
This can easily be done with a container.
For HTTP connection use jarkt/docker-remote-api.
Paul Buonopane [email protected] at NamePros
PGP: https://keybase.io/zenexer
I'm working on cleaning up this advisory so that it's more informative at a glance. Suggestions are welcome.
This advisory addresses the underlying PHP vulnerabilities behind Dawid Golunski's [CVE-2016-10033][CVE-2016-10033], [CVE-2016-10045][CVE-2016-10045], and [CVE-2016-10074][CVE-2016-10074]. It assumes prior understanding of these vulnerabilities.
This advisory does not yet have associated CVE identifiers.
NOTE: The service level and consistency feature is one of the most changed areas of the mymysqlnd_ms fork. Functionalities like server side read consistency and server side write consistency allow transparent migration to MySQL asyncronous clusters in almost all use cases with no or at most extremely small effort and application changes.
Different types of MySQL cluster solutions offer different service and data consistency levels to their users. Any asynchronous MySQL replication cluster offers eventual consistency by default. A read executed on an asynchronous slave may return current, stale or no data at all, depending