[{"_1":2,"_151":-5,"_152":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_130":131},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","routes/_layout.r.$namespace.$reponame",{"_22":23,"_24":-5,"_25":11,"_26":11,"_27":28,"_29":30,"_31":-5,"_32":11,"_33":34,"_83":-5,"_84":85,"_123":-5,"_124":11,"_125":17,"_126":11,"_127":-5,"_128":129},"canonicalUrl","https://hub.docker.com/r/cholzberger/easymysql/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","cholzberger","reponame","easymysql","cloudBuildSource","isAutobuildsAvailable","repo",{"_35":36,"_37":38,"_40":41,"_42":43,"_44":11,"_45":46,"_47":48,"_49":50,"_52":30,"_27":28,"_53":54,"_55":-5,"_56":57,"_58":59,"_60":61,"_62":-5,"_63":57,"_64":65,"_66":11,"_67":28,"_68":69,"_74":17,"_75":76,"_80":28,"_81":82},"categories",[],"content_types",[39],"image","date_registered","2015-05-23T22:30:03.734388Z","description","","is_private","last_updated","2015-08-30T22:19:38.650418Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[51],"application/vnd.docker.distribution.manifest.v1+prettyjws","name","pull_count",354,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# EasyMySQL #\n\n[docker]: https://dev.mysql.com/downloads/workbench/\n\n__A docker container to provide MySQL databases on the fly.__\n\nThis Dockerfile is used to provide MySQL databases in a frictionless\nbut flexible way. The requirement was to provide different\nMySQL based relational databases for computer science students\nfor educational purposes (database/webtechnology lectures and labs).\nNevertheless, the approach can be used\nfor similar purposes in complete different domains.\n\nWhenever you have to\n\n- provide data as a relational database via MySQL\n- with user based access requirement\n- for demonstrational purposes (throw-away database)\n- in an ad hoc way\n\nthis container might be of interest to you.\n\n__Warning: You should not use this container for production purposes.__\n\n## Prerequisites ##\n\nFirst, you have to install [Docker](docker).\n\nIf you are using Linux, you are fine. You will find Docker installation instructions\nfor a lot of Linux distributions [here](http://docs.docker.com/installation/).\n\nBut no worries. If you are using __Windows__ (why ever) or __Mac OS X__ (like me) simply\nfollow the [boot2docker](http://boot2docker.io) installation instructions\nfor\n\n- [Windows](https://github.com/boot2docker/windows-installer/releases) or\n- [Mac OS X](https://github.com/boot2docker/osx-installer/releases)\n\n## Usage ##\n\nTo use this container you have to build an image as a first step. This image provides a self-contained MySQL\nserver. You can clone this repository or tell docker to do the repository handling\nbehind the scenes for you (which is my preferred way in case of github provided\n Dockerfiles):\n\n```Shell\ndocker build -t mysqldb github.com/nkratzke/easymysql\n```\n\nNow you have an image named *mysqldb* on your system, capable to\nprovide MySQL databases. The simplest way to do start a database is like that:\n\n```Shell\ndocker run -d -p 3306:3306 mysqldb\n```\n\nIt will create a running container on your system providing a MySQL server.\n\n- Container will provide a standard database (I use for demonstration purposes in some of my lectures).\n- MySQL server has a user called *student* with a password called *secret*\n- The database is reachable on port 3306 (standard MySQL Port)\n\nIf you want to run your database on a different port than 3306 just do the following:\n\n```Shell\ndocker run -d -p 4407:3306 mysqldb\n```\n\nto run it on port 4407 (for instance). You can figure out that the container is running\n\n```Shell\ndocker ps\n```\n\nand docker returns an output like that.\n\n```Shell\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n85fbad3eb5ce mysqldb:latest \"/usr/local/bin/star 56 minutes ago Up 55 minutes 0.0.0.0:3306->3306/tcp focused_lalande\n```\n\nTo check whether the database is working, you can connect to it.\nFigure out what address your docker host has. If you are working with Boot2Docker\nyou can do this\n\n```Shell\nboot2docker ip\n```\n\nand you will get an answer like that:\n\n```Shell\nThe VM's Host only interface IP address is: 192.168.59.104\n```\n\nNow you have all to connect to your MySQL database. To check that everything is fine\njust start [MySQLWorkbench](https://dev.mysql.com/downloads/workbench/) and\nenter the following parameters when creating a new database connection:\n\n- __Hostname:__ IP address or DNS name of your docker host (when you are working with boot2docker its the ip you get via boot2docker ip)\n- __Username:__ *student* (you can change this, we will come to this later)\n- __Password:__ *secret* (you can change this, we will come to this later)\n- __Default Schema:__ *LVBsp* (you can change the database as well, so stay tuned)\n\nTo stop a container simply figure out its CONTAINER ID (via docker ps as shown above)\nand stop it like that:\n\n```Shell\ndocker stop 85fbad3eb5ce\n```\n\nThe above mentioned standard database is a read only default database. Not very helpful\n(except for me and my lectures).\nBut the container is capable to do more by providing a set of parameters.\n\n- user and password to define your own user\n- right to define whether you want to provide just read or full access rights\n- url to provide an arbitrary sql file (UTF8 encoded) to deliver your own database\n\nSo let's figure out some details.\n\n### Use your own database(s) with url###\n\nYou can provide your own database via a sql file when you start your container.\nJust use the url parameter to point to a valid sql file.\nThis file can be hosted anywhere (accessible from your docker host).\n\n__Attention!__ SQL file is assumed to be encoded as UTF8 and has to valid as well as non interactively processable by mysql.\n\n```Shell\ndocker run -d -p 3306:3306 -e url=\"http://www.example.org/my/database.sql\" mysqldb\n```\n\n### Define user with user and password###\n\nYou can create your own user/password combination by using the user and\npassword parameter.\nBy default the created MySQL user will get read access to all databases hosted by this container.\n\n```Shell\ndocker run -d -p 3306:3306 -e user=\"Nane\" -e password=\"meins\" mysqldb\n```\n\n### Change access rights with right###\n\nYou can change the access rights of your database.\n\n- READ (which is mapped to GRANT SELECT on all databases) __[DEFAULT]__\n- WRITE (GRANT ALL PRIVILEGES WITH OPTIONS on all databases, so this is a power user beeing able to do everything)\n\n__Hint! Access rights have to be written completely in uppercase.\nSo Write is not recognized as WRITE!!!__\n\nBe aware! If you are granting write access to the user, the user is able to do everything\nwith the database including\n\n- create new databases\n- drop existing databases\n- insert and modify data\n- create or drop users\n- changes rights of existing users\n- shutdown databases and so on.\n\nThe read access right is the default one. So\n\n```Shell\ndocker run -d -p 3306:3306 -e right=\"READ\" mysqldb\n```\n\nis synonym to\n\n\n```Shell\ndocker run -d -p 3306:3306 mysqldb\n```\n\nRead access is perfect for providing read-only datasets. E.g. databases for students\nthey should use to answer questions. By providing a database read-only\nit is assured that no student can destroy the database accidentally.\n\nIf you want to create a user with complete write access to your database\nyou can run something like that\n\n```Shell\ndocker run -d -p 3306:3306 -e user=\"Me\" -e password=\"mine\" -e right=\"WRITE\" mysqldb\n```\n\nwhich will provide __full access__ to the database for user *Me*.\n\nWrite access is perfect to provide databases, which can be administered by the\nuser. E.g. for students who have to set up a data model from scratch but should not\nhave to deal with nitty critty MySQL server installation and configuration. Nevertheless\nthey have to be aware that the user can do arbitrary harm to the database.\nSo normally a user with write access should create users with a more restrictive\nset of rights for the database. But this is up to the user.\n\n### Tips for troubleshooting ###\n\nIf you want to provide your own databases, you must assure that your database definition\nfile provided via the url parameter is valid and processable by MySQL as well as \ndownloadable by curl (which is used behind the scenes to do that).\n\nIf it works in MySQL Workbench, it should work with this container.\n\nNevertheless, if your are running into troubles you should start your container\nwith the -t and -i parameter of docker. This will forward the output of the container\nto your console, which is likely to be helpful for debugging purposes.\n\n```Shell\ndocker run -t -i -p 3306:3306 -e url=\"http://www.ex.org/my/database.sql\" mysqldb\n```\n","has_starred","hub_user","immutable_tags_settings",{"_70":11,"_71":72},"enabled","rules",[73],".*","is_automated","permissions",{"_77":17,"_78":11,"_79":11},"read","write","admin","user","storage_size",240033158,"orgData","recentTags",[86],{"_87":39,"_88":89,"_90":91,"_92":93,"_94":95,"_96":97,"_45":112,"_113":89,"_114":28,"_115":51,"_52":116,"_117":118,"_119":103,"_120":112,"_121":61,"_122":17},"content_type","creator",190240,"digest","sha256:4adc24419b94c0ca46aa5253d8dffb98dd7368e5062afeb5c392664f2e05b3d9","full_size",119303047,"id",162571,"images",[98],{"_99":100,"_90":91,"_101":43,"_102":103,"_104":105,"_106":43,"_107":43,"_108":-5,"_109":110,"_58":61,"_111":-5},"architecture","amd64","features","last_pulled","2026-09-10T06:43:49.822322934Z","last_pushed","2015-08-30T22:19:38Z","os","os_features","os_version","size",119303303,"variant","2015-08-30T22:19:39Z","last_updater","last_updater_username","media_type","latest","repository",210623,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_33":132,"_139":140,"_128":149,"_150":11},{"_35":133,"_37":134,"_40":41,"_42":43,"_44":11,"_45":46,"_47":48,"_49":135,"_52":30,"_27":28,"_53":54,"_55":-5,"_56":57,"_58":59,"_60":61,"_62":-5,"_63":57,"_64":65,"_66":11,"_67":28,"_68":136,"_74":17,"_75":138,"_80":28,"_81":82},[],[39],[51],{"_70":11,"_71":137},[73],{"_77":17,"_78":11,"_79":11},"tags",{"_141":59,"_142":-5,"_143":-5,"_144":145},"count","next","previous","results",[146],{"_87":39,"_88":89,"_90":91,"_92":93,"_94":95,"_96":147,"_45":112,"_113":89,"_114":28,"_115":51,"_52":116,"_117":118,"_119":103,"_120":112,"_121":61,"_122":17},[148],{"_99":100,"_90":91,"_101":43,"_102":103,"_104":105,"_106":43,"_107":43,"_108":-5,"_109":110,"_58":61,"_111":-5},[],"canDeleteTags","actionData","errors"]

cholzberger/easymysql

Tags for cholzberger/easymysql