Tagged with #lamb

33 results found.

• Lamb 0.3.0

  Sander July 28, 2023 at 11:43 am

  Introducing Lamb 0.3.0 - Literally Another Micro Blog. This release brings new features, improvements, and bug fixes, making blogging even easier. The update includes Docker support, an optional config.ini with support for menu items to customize your installation, improved documentation, and more.

  Lamb offers a simple, self-hosted single-author blog with a Twitter-like interface, friction-free Markdown entry, discoverable Atom feed, hashtags support, and a 404 fallback URL feature.

  Download the latest release from GitHub and provide your valuable feedback. #lamb #projects

• Lamb 0.2

  Sander March 24, 2023 at 9:46 am

  I've released Lamb 0.2, my micro blogging app that's powering this site.

  What's new?

  • Posts! Posts are statuses with a title. The title can be added in the front matter (front matter is parsed as an ini-string). Posts have a slug based on the title when the post was created.
  • Individual statuses / posts have opengraph tags for improved sharing fidelity.
  • The text editor grows to accommodate the input.

  ‎ #lamb #projects

  More info and download link

• Basic routing using REQUEST_URI

  Sander March 21, 2023 at 12:41 pm

  So for nginx it is not straightforward to setup PHP-FPM so that PATH_INFO is correctly populated. Lamb uses the following /index.php/some/other type routing, where /some/other should be the PATH_INFO. Instead I want to make setup for a variety of web-servers straightforward, so I've switched to the more robust REQUEST_URI. This simplifies nginx configuration and Caddy and the PHP built-in web-server are compatible.

  REQUEST_URI contains everything after the domain name, including the query string, so that needs to be removed:

  $request_uri = '/home';
  if ( $_SERVER['REQUEST_URI'] !== '/' ) {
      $request_uri = strtok( $_SERVER['REQUEST_URI'], '?' );
  }
  

  We can see that for a request for the root of the site, REQUEST_URI returns / whereas PATH_INFO would be empty, so the code above takes that into account. We can then deduct a router action as follows:

  $action = strtok( $request_uri, '/' );
  

  Once the $action is known, it can be checked against an allowed list of actions:

  switch ( $action ) {
      case 'edit':
          ...
          break;
      default:
          respond_404();
          break;

  ‎ #php #lamb