Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118260 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42826 invoked from network); 12 Jul 2022 18:37:19 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Jul 2022 18:37:19 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D01151804B5; Tue, 12 Jul 2022 13:31:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS; Tue, 12 Jul 2022 13:31:54 -0700 (PDT) Received: by mail-ej1-f49.google.com with SMTP id oy13so11505152ejb.1; Tue, 12 Jul 2022 13:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kt2B/TOE/3KhtqnW9g85HAZ2YfFfYA32CpowKoQTxas=; b=WUVU1Ri1ln06NsAyyIcE5EiXyRinN9bZDeCc23EBtzwCa7oJqb1EIXnbWQ3uozLKjy IJTlQQHxmIxOj/8B2cCP+Sh7GBBbN2ZqmhVwOQs7Fv9Tx4JmaLIN4/C4df5g7Ei7P63R iuF9DDz7opAS1Vl2G7/nNEGyj88DMOi2DQEREaiQumLTVKnk4iNbkB2l3g//KFdQE3uR GTXWJW86/hb9Btz86lQC7lRfcAa7VuqAS4P7yC1Jt4Arj4ucQZPlJciGif6zRgZNx2WS S/bvmON7pC9PBWq7tb/tjULFd/FYyb2vMkku6Okgc4GkZWnwKMi4LanzTvDcfYYaTNvW tjVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kt2B/TOE/3KhtqnW9g85HAZ2YfFfYA32CpowKoQTxas=; b=tGBTR/d9lLCvZBU/zRPHHIJY9P7d1HooqvWKcpzn9KWkMBQqAfO4Tnv0XyfdicgqB0 yNfOotH4m+m0IQiizlQbpr4p67j5wemqFgT+pNdAIbJmPa3CA5xsXnSUdVGS9cscuFrI 0cw6vvRHITBrOZkRKHFyfUcZWA3Fp5Hj1EbGuhHxTWQ5EWsDvUb4LOJy55NTH+u3GLrJ cPdJvcoXWC2nk2fSKHJ/s6zwsKNS8ANNLs7Y7QK/MlccYMNHDNOdR0T8CsPQitZjcJ5j RY6pnVSmls/zLwuLr1hVmoWrQ53k9z7wMg+qlACbkIamgAn5egp3014fS1bnM28bKLkY zIdw== X-Gm-Message-State: AJIora8aWw3Wnmpv+Zmpthr5pC8IHpc4tpRcpA+B6S8nTSLsz72GLo3b ZglNSBUT4BQ42yg00vEcAinY2IowuPSxQPorY+c= X-Google-Smtp-Source: AGRyM1vaIgFFDwJlTCOElJJb1YbLzwCkeyRXsYHFZmNCpMNEuZyZzGKKgSdPX080JVtFdAlFdhspKDI8NEm82oA0+SY= X-Received: by 2002:a17:906:2245:b0:715:7c81:e39d with SMTP id 5-20020a170906224500b007157c81e39dmr26437760ejr.262.1657657913052; Tue, 12 Jul 2022 13:31:53 -0700 (PDT) MIME-Version: 1.0 References: <90094848-cf18-1b41-da8d-1abd60461940@gmx.de> <22c8fe8d-b5f3-7284-eedc-01e5232882b8@gmx.de> <2a0ef561-d0fc-62e8-7c79-548ccdb67cb6@gmx.de> In-Reply-To: Date: Tue, 12 Jul 2022 22:31:15 +0200 Message-ID: To: "Christoph M. Becker" Cc: james@asgrim.com, Calvin Buckley , Ayesh Karunaratne , PHP Developers Mailing List , internals-win Content-Type: multipart/alternative; boundary="00000000000011129d05e3a18ff2" Subject: Re: [PHP-DEV] Windows PECL build machine died From: divinity76@gmail.com (Hans Henrik Bergan) --00000000000011129d05e3a18ff2 Content-Type: text/plain; charset="UTF-8" i have a 40-core 128GB RAM server with 1 (and only 1) static ipv4 address that I intend to keep around until at least 27 november 2025 (but unsure after that), it has more RAM/CPU than i need, and i could set up a virtual machine on it and give VNC access to the VM in the form of > ssh -L 9999:localhost:3389 user@ip then point a RDP/VNC client to localhost:9999 i can dedicate individual TCP ports to it, but not any of 22, 80, 443, 5900, 5901, 8083, 9999, 587, 2525 (after which i can recommend Teamviewer for a more comfortable access) but the server has several caveats: - it's un-raided, rolling just a single 1TB SSD, if that SSD was to die, everything on it would be lost, and it would probably take days to replace the drive. - it's located in a somewhat unstable environment, occasional power outage, it was out on 30 june, 23 june, 27 january, and in 2021 was down on 30 august. (it boots up and recovers automatically, but it has a reboot time of roughly 300 seconds until ssh responds again) - I can not offer a dedicated IP (but can offer some dedicated ports) - May be decommissioned after 27-11-2025 If that sounds like a good idea, I'll want a ssh public key. On Tue, 12 Jul 2022 at 15:38, Christoph M. Becker wrote: > On 11.07.2022 at 21:04, Hans Henrik Bergan wrote: > > > Any of you windows.php.net guys familiar with SSH? Can one be created? > > That would be possible (needed to be set-up by Alex Schoenmaker), but > while that could solve the upload issue, it wouldn't solve the other > issue I've mentioned, namely that we need to avoid dynamically linking > against incompatible versions of dependencies. And there is yet another > issue, namely security. I think these issues can only be solved by some > central place where the packages are build. > > > On Mon, 11 Jul 2022 at 19:52, Christoph M. Becker > wrote: > > > >> On 11.07.2022 at 18:53, Hans Henrik Bergan wrote: > >> > >>> Is there any SSH public key associated with the Windows php developers? > >> Or > >>> with CMB? > >> > >> No. At least not regarding windows.php.net. > >> > >>> On Mon, 11 Jul 2022 at 18:25, Christoph M. Becker > >> wrote: > >>> > >>>> On 11.07.2022 at 17:41, Hans Henrik Bergan wrote: > >>>> > >>>>> Do you mean it is unlikely that Github Actions will suffice? because > >> that > >>>>> would definitely be a great solution if it was possible/feasible . > >>>> > >>>> No. It is only unlikely that automated uploads to window.php.net > will > >>>> ever be possible using GH actions. > >>>> > >>>>> Anyway, with regards to "I don't think there are special requirements > >>>>> regarding the hardware", can you give a rough estimate on RAM/disk > >> space > >>>>> requirements? > >>>> > >>>> The old machine had something like 4 or 8 GB RAM, and a 128 GB hard > >> disk. > >>>> > >>> > >> > > > > --00000000000011129d05e3a18ff2--