* Add example to use MySQL in local without SSL
* Update 4.0/docs/fluent/overview.md
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
* Update 4.0/docs/fluent/overview.md
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
* Created transaction documentation
Added documentation for the transaction syntax, based on the 3.0 documentation and current implementation.
Added the Star model as example model, as it is used throughout the Fluent examples.
* Apply suggestions from code review
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
I ran into an issue where `PRAGMA foreign_keys = ON` was required on the database itself. I was unaware of this, as it worked for Vapor. I added a tip containing problems that can occur when querying the database directly.
* added small tip regarding query params
* Implemented @0xTim suggestions
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
Co-authored-by: Tim Condon <0xTim@users.noreply.github.com>
The example in authentication -> Fluent first establishes code that checks wether a user’s password is at least 8 characters long, and then uses a 6 character password in the example. This is not a huge problem, but it might present a stumbling block for readers who didn’t pay close attention to the code.
* Update references to `app.swift`
When performing `vapor new hello -n` command as part of [Getting Started](https://docs.vapor.codes/4.0/hello-world/), an `app.swift` file is not generated. The code that creates and runs the `app` lives in `main.swift`. This updates the documentation to reflect this.
* Moved reference to `main.swift` file under "Run"
Created a `### Run` heading, moving the information about `main.swift` under there to match the folder structure on disk.
* Add Custom Working Dir page
Add a page with images explaining how to set a custom working directory in Xcode.
* Fix “Xcode” spelling
* Move custom working dir doc to Xcode section
* Add section intro and change formatting.
* Update xcode.md
Co-authored-by: Tanner <me@tanner.xyz>
The previous instructions suggested that you could continue with "Build & Run" as soon as Xcode opens, but this is not correct and the Play button is at this point greyed out as unavailable, as is selecting "Build and Run" from the menu, as dependencies are still being downloaded. This could lead users inexperienced with Xcode to think they have done something wrong when they just need to wait a minute or so. This seems likely the cause of at least one comment I saw on Vapor discussion somewhere today when searching for a new user guide (sorry, location lost) where the new user stated that Step 2 of these instructions did not work.
This change also correctly identifies the expected output will be in the Xcode console, and not in the "terminal".