Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix more links broken by Couscous #1071

Merged
merged 3 commits into from
Oct 24, 2021
Merged

Fix more links broken by Couscous #1071

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8958852
Fix links broken by Couscous
jdreesen Oct 24, 2021
f18e433
Fix links broken by Couscous
jdreesen Oct 24, 2021
a463368
Fix links broken by Couscous
jdreesen Oct 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/environment/custom-domains.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,6 @@ After waiting for the DNS change to propagate (sometimes up to several hours) yo
Some applications serve static files hosted on AWS S3. You can read the [Websites](/docs/websites.md) documentation to learn more.

If you want to host a fully static website with HTML files or a Single Page Application (eg. built with Vue, React or Angular)
you may be interested in [the Static Website construct of the Lift plugin](https://github.com/getlift/lift/blob/master/docs/static-website.md).
you may be interested in <a href="https://github.com/getlift/lift/blob/master/docs/static-website.md">the Static Website construct of the Lift plugin</a>.

This allows to configure custom domains, root domain to `www` redirects and more. Check out [the official documentation](https://github.com/getlift/lift/blob/master/docs/static-website.md) for more details.
This allows to configure custom domains, root domain to `www` redirects and more. Check out <a href="https://github.com/getlift/lift/blob/master/docs/static-website.md">the official documentation</a> for more details.
6 changes: 3 additions & 3 deletions docs/frameworks/laravel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,12 +89,12 @@ For more details follow [the "Console" guide](/docs/runtimes/console.md).
## Assets

To deploy Laravel websites, assets need to be served from AWS S3. The easiest approach is to use the
[Server-side website construct of the Lift plugin](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
<a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Server-side website construct of the Lift plugin</a>.

This will deploy a Cloudfront distribution that will act as a proxy: it will serve
static files directly from S3 and will forward everything else to Lambda. This is very close
to how traditional web servers like Apache or Nginx work, which means your application doesn't need to change!
For more details, see [the offical documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works).
For more details, see <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works">the official documentation</a>.

First install the plugin

Expand Down Expand Up @@ -139,7 +139,7 @@ Now deploy your website using `serverless deploy`. Lift will create all required
uploading your assets to S3 automatically.

For more details, see the [Websites section](/docs/websites.md) of this documentation
and the official [Lift documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
and the official <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Lift documentation</a>.

### Assets in templates

Expand Down
6 changes: 3 additions & 3 deletions docs/frameworks/symfony.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,12 +139,12 @@ in `trusted_proxies`.
## Assets

To deploy Symfony websites, assets need to be served from AWS S3. The easiest approach is to use the
[Server-side website construct of the Lift plugin](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
<a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Server-side website construct of the Lift plugin</a>.

This will deploy a Cloudfront distribution that will act as a proxy: it will serve
static files directly from S3 and will forward everything else to Lambda. This is very close
to how traditional web servers like Apache or Nginx work, which means your application doesn't need to change!
For more details, see [the offical documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works).
For more details, see <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md#how-it-works">the official documentation</a>.

First install the plugin

Expand Down Expand Up @@ -203,7 +203,7 @@ upload all specified files and directories to the bucket.
> If you are not using Flex, update the `serverless.yml` file to exclude assets from the deployment ([see the recipe](https://github.com/symfony/recipes-contrib/blob/master/bref/symfony-bridge/0.1/serverless.yaml#L35))

For more details, see the [Websites section](/docs/websites.md) of this documentation
and the official [Lift documentation](https://github.com/getlift/lift/blob/master/docs/server-side-website.md).
and the official <a href="https://github.com/getlift/lift/blob/master/docs/server-side-website.md">Lift documentation</a>.

### Assets in templates

Expand Down