阅读背景:

从AWS上的symfony动态站点过渡到具有扁平CMS的静态站点

来源:互联网 

Complete newb here. First question asked. Not a developer. Please bare with me!

在这里完成newb。第一个问题。不是开发人员。请和我一起露营!

We have a large site (100k+ pages) that was built with symfony 1.2.8 and currently hosted on AWS. We have no further plan of developing the site or keeping it in it's current form, and want to bring down server costs to a minimum. Our thinking is to salvage the data and turn it into a static HTML site, so it can be hosted on a (much) cheaper server infrastructure.

我们有一个大型网站(100k +页面),它是用symfony 1.2.8构建的,目前托管在AWS上。我们没有进一步的计划来开发网站或保持其当前形式,并希望将服务器成本降至最低。我们的想法是挽救数据并将其转换为静态HTML站点,因此它可以托管在(更便宜)的服务器基础架构上。

Some questions we have in mind are:

我们想到的一些问题是:

  1. What is the best way to do that that will keep the URL of each page intact, and also keep the SEO juice each has?

    这样做的最佳方法是保持每个页面的URL完整,并保持每个SEO汁液的最佳方式是什么?

  2. What is the easiest way to make those static pages searchable?... can google's custom search engine be an answer?

    使这些静态页面可搜索的最简单方法是什么?...谷歌的自定义搜索引擎可以作为答案吗?

  3. If we want to have minimal CMS capabilities, would using what's referred to as "flat CMS" be a good way to do it?... If so, how would the transition look like?

    如果我们希望拥有最小的CMS功能,那么使用所谓的“平坦CMS”是一个很好的方法吗?...如果是这样,转换将如何?

  4. Is there a way to dump the content (by category/type) from the original site into some sort of data package that can be repurposed in other frameworks/CMSes?

    有没有办法将内容(按类别/类型)从原始站点转储到某种可以在其他框架/ CMS中重新使用的数据包?

Thanks for your thoughts on this!

谢谢你对此的想法!


Related questions: How to Archive a Dynamic (PHP) Website as Static HTML? --- Converting a dynamic PHP/mySQL website to an archived HTML version? --- PHP Website Converted to Static HTML site - Linking Issue

相关问题:如何将动态(PHP)网站存档为静态HTML? ---将动态PHP / mySQL网站转换为存档的HTML版本? --- PHP网站转换为静态HTML网站 - 链接问题

1 个解决方案

#1


0  

  1. You can host the pages in S3. As long as the html files keep the same structure you should be able to keep your URL structure. Also place AWS Cloudfront in front of S3 to allow HTTPS and custom content rules. With Cloudfront you can also map legacy URL's to different paths in S3 buckets to give you a bit more flexibility.
  2. 您可以在S3中托管页面。只要html文件保持相同的结构,您就应该能够保留URL结构。同时将AWS Cloudfront置于S3前面以允许HTTPS和自定义内容规则。借助Cloudfront,您还可以将旧版URL映射到S3存储桶中的不同路径,从而为您提供更大的灵活性。

  3. As long as these are static pages, they are searchable in Google. You can make a sitemap.xml in the root that lists all these pages to make it easier for Google to find (add them in google webmaster tools)
  4. 只要这些是静态页面,它们就可以在Google中搜索到。您可以在根目录中创建一个sitemap.xml,列出所有这些页面,以便Google更轻松地找到它们(在Google网站管理员工具中添加它们)

  5. You can use Instant. Which offer content management for static websites. You only have to add a javascript to the site to make it work.
  6. 你可以使用Instant。哪些提供静态网站的内容管理。您只需要向网站添加javascript即可使其正常运行。

  7. That highly depends on the CMS. I don't have experience with symfony, so I don't have the answer. There should probably be some export, or maybe you could use a website scraper to download the website as HTML.
  8. 这在很大程度上取决于CMS。我没有symfony的经验,所以我没有答案。应该有一些导出,或者你可以使用网站刮刀下载HTML网站。


分享到: