Problems with Statamic Install #10487
-
|
Hi all, I have been trying to get Statamic installed and working, but I keep running into problems I cannot get passed. The Quick Start suggested I come here and ask, so that's what I am doing; hoping that someone here can help me. I am trying to install Statamic in a Docker container of my own so I can host in Portainer in my VMware ESXi server and then use lsyncd or Mutagen to sync the source files between my laptop and the VM. I posted all the relevant configuration files I am using to this Gist: https://gist.github.com/mikeschinkel/cc5bfdff3bc3d35794f0551460965391 The first problem I have — though not a blocker — is that the assets are being served as HTTP instead of HTTPS. From line 8 of the view source: The second problem — which is a blocker — is I get this error this when I try to access the control panel: There is a There is also a message that says run I did try to get I then tried three (3) different starter kits — I just want to get Statamic up so I can see what it is like and be able to use xdebug to learn Laravel and Statamic. Note that I have lots of PHP and other backend coding experience (Golang, for example) but zero Laravel or Statamic experience and very little front-end dev experience before trying to get this working. I really don't want to give up on Statamic, but I am at a loss for how to get a working site at this point. So thank you in advance for any help on this. -Mike |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 36 replies
-
😄 Definitely sounds like you're going for a fairly complex initial approach - if you're just testing it out then ideally you'd want to just fire up something local (such as Laravel Herd or Valet) rather than throwing all sorts of potential npm, environment, docker and nginx issues into the mix. The Quick Start references some more in-depth guides: https://statamic.dev/installing - really the quick-start is much more geared for local development. In saying all that, have you checked your |
Beta Was this translation helpful? Give feedback.
-
I am sure I can try. But since I started with Statamic I don't know how to do that yet. I'll look into that. |
Beta Was this translation helpful? Give feedback.
-
|
Do this: https://laravel.com/docs/11.x#creating-a-laravel-project. |
Beta Was this translation helpful? Give feedback.
-
Oh, okay. Thank you for explaining that. Seems obvious, in hindsight. OTOH, it is really easy to get overwhelmed when things a person is new to don't work.
Here's a gist showing that and the |
Beta Was this translation helpful? Give feedback.
-
To clarify, I am dropping into a terminal shell prompt and using |
Beta Was this translation helpful? Give feedback.
-
Okay, I was able to get that to work, no problem, given my experience trying to get Statamic working. It is running as a Docker container in Portainer on a Debian VM hosted by VMware ESXI server in my homelab and serving from It only displays one page with external links, but then I assume that is what should be expected? 
BTW, thank you for helping. I really appreciate it. |
Beta Was this translation helpful? Give feedback.
-
|
I highly recommend just using Herd instead of Docker if you’re just trying to try Statamic out. all of your problems would disappear and we’d be able to help if they didn’t. Docker is a black hole of infinite configurability and we have very little experience with it here. I hope you’re okay trying one more new thing in the mix!
|
Beta Was this translation helpful? Give feedback.
-
So I decided to at least give Herd a try. I followed the instructions for installing Statamic with Herd and immediately hit a brick wall string to install Statamic CLI which seems like a problem with dependencies in $ composer global require statamic/cli
Xdebug: [Step Debug] Could not connect to debugging client. Tried: 127.0.0.1:9003 (fallback through xdebug.client_host/xdebug.client_port).
Changed current directory to /Users/mikeschinkel/.composer
./composer.json has been updated
Running composer update statamic/cli
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- symfony/console v4.3.3 requires php ^7.1.3 -> your php version (8.3.9) does not satisfy that requirement.
- psy/psysh v0.9.9 requires symfony/console ~2.3.10|^2.4.2|~3.0|~4.0 -> satisfiable by symfony/console[v4.3.3].
- psy/psysh is locked to version v0.9.9 and an update of this package was not requested.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require statamic/cli:*" to figure out if any version is installable, or "composer require statamic/cli:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I am running PHP |
Beta Was this translation helpful? Give feedback.
-
|
Yup you've got some older packages in there. If you're not using them, you can get rid of everything from that composer.json file (in `~/.composer) and start again. Composer is a big part of Laravel dev so it's a good skill to get. FYI, this is really nothing to do w/ Statamic, this is a composer issue. You'd have the same issue trying to install any global composer package. |
Beta Was this translation helpful? Give feedback.
-
|
Nevermind. I just realized there was an old, old version of |
Beta Was this translation helpful? Give feedback.
-
|
@edalzell — Thanks, our messages crossed. 🙂 |
Beta Was this translation helpful? Give feedback.
-
BTW, most of my experience with PHP was backend-dev for WordPress and writing plugins. I developed a love-hate relationship with Composer because it was always causing dependency issues when I had to use it that I struggled to resolve in part because I did not use it often enough. Back to today — too long of a story for now, but — my interest in Statamic is for a large Laravel-based CMS to work with so I could write some tools for PHP and Composer. But, as I implied, that is a story for another day. |
Beta Was this translation helpful? Give feedback.
-
|
OKAY, after much pain and bullheaded effort, I was able to get it all working and figure out what caused the problems for future visitors and maybe even for updated Statamic documentation. Serving HTTPS URLsFirst question was "How to force Statamic to serve HTTPS URLS?" That one was easily answered and had nothing to do with using Docker vs. Herd. I needed to add a call to Here is what that file looks like after I updated it: <?php // <root>/app/Providers/AppServiceProvider.php
namespace App\Providers;
use Illuminate\Support\Facades\URL;
use Illuminate\Support\ServiceProvider;
use Statamic\Statamic;
class AppServiceProvider extends ServiceProvider
{
/**
* Register any application services.
*/
public function register(): void
{
//
}
/**
* Bootstrap any application services.
*/
public function boot(): void
{
URL::forceScheme('https');
// Statamic::vite('app', [
// 'resources/js/cp.js',
// 'resources/css/cp.css',
// ]);
}
} |
Beta Was this translation helpful? Give feedback.
-
|
@edalzell — I hear ya. and empathize. Maybe a moderate approach is to document those things that you find your users have issues with, and ignore those you don't hear about from your users? BTW, in this case if you made an |
Beta Was this translation helpful? Give feedback.
-
|
Statamic doesn’t control the appserviceprovider, so I can’t really have anything in there. And you don’t really want to do that in a package because it’s hidden and you don’t know how folks have things set up. That’s why I suggested improving the docs via a PR. |
Beta Was this translation helpful? Give feedback.
-
|
I think a big chunk of this is that realistically people handle http > https a thousand different ways. Can redirect in apache, nginx, caddy etc. Can forward ports. Can do it via Every single example on the deployment page (Ploi, Forge, Docker Sail etc) handles it in a different way. Many people do want http on the site itself because they'll have a proxy in front handling https. Theres just so many different bespoke configurations - so Statamic/Laravel largely take a naive approach. Something to consider is that if it was set as an environment variable then while it might have worked for you it would have likely broken everyone elses setups where its largely auto-detecting. And could give the false impression that setting |
Beta Was this translation helpful? Give feedback.
-
|
@sjclark — There are two sides to HTTP.
I am concerned about content generation, not about listening, serving, and/or redirecting (my Traefik and Step-CA already handles that later, nicely.)
Well, I definitely am not 100% familiar with how things are done in the Laravel world but in other web scenarios I am familiar with people rarely want to serve However, from what I have seen before, and recently, the Laravel world appears to be walled garden — much like the WordPress world that I am more familiar with — where things are handled the Laravel way in its own ecosystem in its own ways — Herd and Sail and Forge and Envoyer, etc. — and those ways often differ from how others not in the ecosystem do things. So maybe you are correct when it comes to Laravel users; they want to do it the Taylor Otwell way. Of course, if you are interested in growing Statamic beyond existing Laravel users, expecting everyone to do it the Laravel way might not be a palatable approach beyond the Laravel faithful. 🤷♂️
I think most people setting up a web server know that generating HTTPS links does not make a site secure, especially considering the browser will tell them it is not secure the first time they visit such a page when there is no valid SSL certificate. So frankly I do not buy false impressions as a reasonable argument against making it easier to generate HTTPS in the content. #fwiw That said, I have just been offering my perspective as I know it can be good for those on the inside to get an outsider's perspective from time to time because those on the inside can never know what it is like anymore to see their thing with a fresh set of eyes. But I am getting the sense that my input may not be appreciated, and if that is the case then just be explicit and I can move along. |
Beta Was this translation helpful? Give feedback.
-
|
@edalxell —
I assumed Laravel would allow developers to extend it, so I googled and found that Laravel documents how to create your own providers. I decided to do a proof-of-concept to see if in fact it would work and sure enough, it works exactly as I expected it to, side-by-side with an unmodified <?php
namespace App\Providers;
use Illuminate\Support\Facades\URL;
use Illuminate\Support\ServiceProvider;
class HttpsProvider extends ServiceProvider
{
public function register(): void
{
}
public function boot(): void
{
if (env('GENERATE_HTTPS', false)===true) {
URL::forceScheme('https');
}
}
}Is there some reason why Statamic could not add its own provider?
But couldn't the same argument be made against any setting in Only speaking for myself, of course, but the first place I would look for settings — if I was trying to change something, or trying to understand why it behaves the way it does — would be in the settings file, and
As I said before, that's potentially in the cards too |
Beta Was this translation helpful? Give feedback.
-
Missing Control Panel Assets including
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for sticking with this process. I wish you didn't have so much trouble, but I'm working through improving the docs right now so hopefully it doesn't happen to someone else. You are mostly right in that I see Statamic as a CMS that happens to be based on Laravel — but there is also a balance of not recreating the wheel with the enormous amount of things Laravel does provide for us. We used to simple defer to the Laravel docs in a lot of place, but over the years we've been duplicating/elaborating on their content in places to make it more clear and simple to use Statamic. I don't think it's possible to be all one way or other with it, but it is in everyone's best interest to smooth out all the speed bumps possible. So again, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
I've added a page to the docs to help with this specific issue: https://statamic.dev/troubleshooting/missing-control-panel-assets |
Beta Was this translation helpful? Give feedback.
-
|
@jackmcdade & @jasonvarga — Thank you for your responses, and for updating the docs. BTW, that new page is EXCELLENT! Yes, I can see how much of an uphill climb it would be to duplicate all of Laravel's efforts — if for no other reason than how prolific Taylor Otwell is! And I empathize. Maybe the best way to think about it is to set up mission and vision statements — assuming you do not already have them — and then focusing your docs on achieve your vision, as opposed to duplicating Laravel's. More specifically, that means providing docs that target those who are building, deploying, maintaining, administering, and using a CMS vs. developing, deploying, and maintaining a PHP app. IOW, assuming your mission is "To provide the best choice of CMS for <your target market>" and your vision is for "Every new CMS deployment by <your target market> will be a Statamic install" then decide what actions to pursue and decisions to make based on how well they support your mission and vision. Then your choices on what docs to provide/update will naturally be driven by and fall out of what fits your mission and vision. If it supports your mission and vision but duplicates Laravel's efforts, then I suggest you still consider doing it. However, I suspect that if you make choices through that lens of mission and vision you will find that most often you won't need to be duplicating Laravel's efforts directly but instead uniquely catering to your desired audience. -Mike |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I noticed that your "Recent Updates" section on your docs home page lists updated pages but not new pages like the one you linked above. Were you aware of that and/or is that intended? Just thought I'd mention it if you were not aware. |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem with manifest.js Illuminate\Foundation\ViteManifestNotFoundException I used this commands. npm install , npm run dev, npm build. But no one of them not helped for me. What do I need to do? |
Beta Was this translation helpful? Give feedback.
-
|
This guide might be helpful: https://statamic.dev/troubleshooting/missing-control-panel-assets |
Beta Was this translation helpful? Give feedback.
Missing Control Panel Assets including
manifest.jsonThe second problem — the blocker — was much harder to track down and diagnose.
For the answer to the first problem — Serving HTTPS URLs — see here.
TLDR; Running
composer create-projectindocker builddisables plugins and thus fails to load pixelfear/composer-dist-plugin and thus fails to copy over thedistassets, thus causing the control panel to throw blocking errors.The solutions are to either:
ENV COMPOSER_ALLOW_SUPERUSER=1beforeRUN ..., ORRUN composer create-project ...orRUN statamic new ...inRUN script -q -c "<command goes here>".Both of the above will stop Composer from disabling plugins during
docke…