![]() ngninx with the right cache headers), a static site on a single server should handle any reasonable amount of traffic. A static site increases your hosting options and will generally scale very cheaply and easily. I decided early on that I wanted the site to be entirely static. It would be a very fun exercise and would make for a good write up on its own, but you probably would not get much writing done until it's finished. The opposite extreme would be writing your own blogging software. There is no real set up work involved ( just sign up and optionally pick a theme) and nothing new to experiment with. On the low end of the fun scale ( arguably negative fun.) is using a hosted service like Tumblr. A decent gauge of whether something is going to be fun is whether you'd want to listen to someone else describe the set up process. The more twists, turns, and hacks to set it up, the more fun you're going to have. The "fun" factor of setting up a new website is derived from the new ( to you) technology you get to experiment with. There's a high correlation between new and fun. Like any good technologist I'd like to use this as an opportunity to experiement with new technologies. Newīy "new" I'm referring to technology choices that are new to not just me, but the world as a whole. If they're not show stoppers then that would probably increase the "fun" factor though. On the contrary, the newer the platform the more likely there will be complications with the initial setup. Note that being "easy" does not refer to the initial setup of the platform. This usually means it should be git push style deploy. Publishing should be as simple as possible, preferably from the command line. Since a big part of writing is minimizing distraction ( so you can actually focus on writing), it's important to have an efficient way to "test" your posts ( i.e. Saavy readers will recognize this as the writing equivalent of a REPL. View what it'll look like in the browser.The ideal workflow for writing will look something like this: ![]() EasyĮasy in this context means it should be easy to preview an article while writing and the final deployment step should be automated. You use it to either run a dynamic site ( ex: Wordpress or Ghost) or a static site ( ex: nginx serving a pregenerated site). Heroku gives you a free web dyno per application. The bill for it is literally pennies a month and, since it's on S3, we never worry about scaling it up to handle large influxes of traffic.Įven sites with dynamic content can be hosted for free or relatively cheaply. You can also use services like Amazon S3 to host a website for next to nothing.įor example our company's website,, is a static site hosted on Amazon S3. In 2014 there are many options for cheap hosting so cost was not much of a concern.įor static content there are a number of free hosting options such as Tumblr or GitHub pages. In my case, I'd use a number of platforms in the past and had reduced my core requirements list to the following ( in order of importance): Additionally, the more technologically inclined you are, the more time you'll spend on this decision. ![]() Besides the topic and posts themselves, this is probably the most important decision. When setting up a new blog one of the most important ( and fun) decisions you get to make is the tech stack that will run it. To put it another way: it's a riddle, wrapped in a mystery, inside an enigma. I am posting a similar request on the Hibernate forum.This post goes into the technical components of setting up this blog and some of the merits of the tech stack choices.įor the impatient, the final choice of stack is a Pelican powered static site, styled with a modified Octopress theme, deployed via Dokku, running nginx in a Docker container, and it's all deployed to DigitalOcean droplet. If not, can you suggest a different approach that uses a Unix socket? Is what I am trying to do (Hibernate, JDBC, PostgreSQL,, Unix socket) possible? If so, kindly give me some guidance. Which I take to mean that the config file is unusable. "message": ".config.ConfigurationException: Unable to perform unmarshalling at line number 0 and column 0 in RESOURCE. If I ignore the error and try to use config file I get this error: (Of course I have tried many variations such as inserting semicolons in various places, quoting the argument, using square brackets and so on.) The reference to entity "socketFactoryArg" must end with the ' ' delimiter. The XML validator in Eclipse is flagging this error: Jdbc:postgresql:kokodoko?socketFactory=.socketfactory.PostgresqlAFUNIXSocketFactory&socketFactoryArg=/var/run/postgresql/.s.PGSQL.5432 I have referred to this doc:Īnd have been trying entries in along these lines: I am trying to configure Hibernate to use a Unix socket connection to my local PostgreSQL installation. I hope it is appropriate to send this question to this address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |