@allanwhite @NadiehBremer You mean the format you've used in a _redirects file instead of in the netlify.toml?
This rule should totally work regardless of if you set it in a _redirects file or via netlify.toml, but in the toml, it would have to be expressed in valid toml format.
https://github.com/toml-lang/toml
Who's got two thumbs and really enjoyed speaking at @render_conf?
https://www.flickr.com/photos/whiteoctevents/40317737574/in/album-72157667111416898/
https://www.flickr.com/photos/whiteoctevents/40317737574/in/album-72157667111416898/
@NadiehBremer Oh yeah!
There's no way to do that automatically via the Netlify admin UI, but you can serve each site on Netlify, then gather them together in your main site via redirects. You'll need to take care of your root URLs in paths, of course.
I recommend a netlify.toml for configs
There's no way to do that automatically via the Netlify admin UI, but you can serve each site on Netlify, then gather them together in your main site via redirects. You'll need to take care of your root URLs in paths, of course.
I recommend a netlify.toml for configs
@NadiehBremer I can sit patiently and wait until you are ready to share.
⌘R
⌘R
⌘R
⌘R
⌘R
⌘R
... enough. I need to see it right now!
⌘R
⌘R
⌘R
⌘R
⌘R
⌘R
... enough. I need to see it right now!
@Jack_Franklin Real stories and experience make for fascinating talks when they bring practical lessons and insights.
Like your talks do.
Gutted that I can't attend this due to travel. It's going to be ace.
Like your talks do.
Gutted that I can't attend this due to travel. It's going to be ace.
@igloo_si @NetlifyCMS @gitchat A lot of the people in there are based in the US... pretty sure that it will get more lively later in the day.
@igloo_si Hey Jani. I'm afraid I'm not 100% sure. I bet the nice people in the @NetlifyCMS @gitchat channel would be able to give a more informed response though:
https://gitter.im/netlify/NetlifyCMS
https://gitter.im/netlify/NetlifyCMS
@slicknet A popular approach to this on @Netlify is to use a combination of publish dates in the SSG, deploy hooks, and a remote scheduled request to the deploy hook from something like @zapier.
@flaviocopes has a nice explanation: https://flaviocopes.com/netlify-auto-deploy/
(@jekyllrb supports this too)
@flaviocopes has a nice explanation: https://flaviocopes.com/netlify-auto-deploy/
(@jekyllrb supports this too)
@Zeke8990 @NetlifyCMS @contentful @datocms @kenticocloud @prismicio @graph_cms Absolutely! The hard part is convincing clients that a #headlessCMS is a viable alternative to a big, expensive, well-known, monolithic CMS.
They can often be a far better fit, and provide far greater utility, security and performance. I've been advocating for this since 2012.
They can often be a far better fit, and provide far greater utility, security and performance. I've been advocating for this since 2012.
@malavya88 @drupdotes @stevector @Netlify Might this be what you're looking for?
https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
OUCH. If you maintain the moving parts of server infrastructure that you expose to the world, you'd better know how to mitigate this kind of issue.
http://www.zdnet.com/article/update-drupal-asap-over-a-million-sites-can-be-easily-hacked-by-any-visitor/
http://www.zdnet.com/article/update-drupal-asap-over-a-million-sites-can-be-easily-hacked-by-any-visitor/