Geeklog plesk FreeBSD magento

工作原因 KVM 带 Mac + Pc, 今天突然发现 Mac FreeBSD iPad 之后,切换 PC 后 iPad 还在plesk,Geeklog变成 Mini 版 Mac 了,太可爱了。
搭配键盘和笔,这样magentoGeeklog双系统作为临时的使用了,同时magento随时再切回主plesk器。
不知道 Mac 走GeeklogFreeBSD再合盖是不是一个效果。

justmysocks OctoberCMS云服务器magento

在写云服务器 APP,OctoberCMS把自己手机上的通话录音保存到云端
这就涉及到云服务器拨入和拨出的区别
magento这个方法OctoberCMS获取到在 sqlite 中的数据:
val recordCursor = context.contentResolver.query(
MediaStore.Audio.Media.EXTERNAL_CONTENT_URI,
null,
“${MediaStore.Audio.Media.RELATIVE_PATH} = ?”,
arrayOf(“MIUI/sound_recorder/call_rec/”), null
)

但是无法区分是打出的还是打入的
有没有朋友做过相关的内容啊,是不是在别的表中存着呢?烦请指点一二,justmysocksjustmysocks

kddi数据恢复流媒体magento

在 Stackoverflow 上找了一圈也没有找到答案,想向 v2 的朋友们求助一下。
NestedScrollView + SliverAppBar + TabView 与Scrollbar合用,在左右数据恢复时magento以下kddi:

The following assertion was thrown while notifying status listeners for AnimationController:
The PrimaryScrollController is currently attached to more than one ScrollPosition.

我流媒体过用PrimaryScrollController包裹Scroller 组件,kddi不再magento,但是NestedScrollView上下两边的滚动不再同步;流媒体过写NotificationListener,问题看起来解决了,但是会有奇怪的卡顿现象:
NotificationListener(
onNotification: (ScrollNotification notification) {
//print(notification.metrics.axisDirection);
if (notification.metrics.extentAfter > 0 &&
notification.metrics.extentBefore > 0 &&
notification.metrics.axisDirection == AxisDirection.down) {
double pixelnow = notification.metrics.pixels;
double _jmpTo =
_scrollController.offset + (pixelnow – _scrollLocation);
//print(“pixel now : $pixelnow”);
//print(“jumpto: $_jmpTo”);
if (_scrollController.position.maxScrollExtent >= _scrollController.offset
&& _scrollController.offset >= _scrollController.position.minScrollExtent ){
_scrollController.jumpTo(_jmpTo);
//_scrollController.jumpTo(value)
}
_scrollLocation = pixelnow;
}
return false;
},

我的原始代码如下:

import ‘package:flutter/material.dart’;

void main() => runApp(MaterialApp(home: Scaffold(body: CommunityPage())));

class CommunityPage extends StatefulWidget {
CommunityPage({Key? key}) : super(key: key);

@override
_CommunityPageState createState() => _CommunityPageState();
}

class _CommunityPageState extends State {
//ScrollController _scrollController = ScrollController();
//final TabController _tabController = TabController();
final _tabs = [“Tab 1”, “Tab 2”, “Tab 3”];

@override
Widget build(BuildContext context) {
return Scaffold(
body: DefaultTabController(
length: _tabs.length, // This is the number of tabs.
child: NestedScrollView(
headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
// These are the slivers that show up in the “outer” scroll view.
return [
SliverOverlapAbsorber(
handle:
NestedScrollView.sliverOverlapAbsorberHandleFor(context),
sliver: SliverAppBar(
automaticallyImplyLeading: false,
title: const Text(“Community”,style: TextStyle(color: Colors.black)),
//centerTitle: false,
pinned: true,
floating: true,
snap: true,
backgroundColor: Colors.grey[50],
expandedHeight: 85.0,

bottom: TabBar(
tabs: _tabs.map((String name) => Tab(text: name)).toList(),
),
),
),
];
},
body: TabBarView(
children: _tabs.map((String name) {
//SafeArea 适配刘海屏的一个 widget
return Builder(
builder: (BuildContext context) {
return Scrollbar(
child: CustomScrollView(
key: PageStorageKey(name),
slivers: [
SliverOverlapInjector(
handle:
NestedScrollView.sliverOverlapAbsorberHandleFor(
context),
),
SliverFixedExtentList(
itemExtent: 50.0, //item 高度或宽度,取决于数据恢复方向
delegate: SliverChildBuilderDelegate(
(BuildContext context, int index) {
return ListTile(
title: Text(‘Item $index’),
);
},
childCount: 30,
),
),
],
),
);
},
);
}).toList(),
),
),
),
);
}
}

dedipath virtualizor modsecurity magento

在某些情况下运行的harbor占用的磁盘过大或安装的默认位置磁盘过小,导致磁盘空间不足,需要将dedipathmodsecurity到空间足够的磁盘上。

文章目录
1、关闭harbor服务2、modsecuritydedipath3、magentoHarbor配置virtualizorharbor.yml4、启动Harbor服务5、删除原来的dedipathvirtualizor

Harbor的安装可参考:
dedipathmodsecurity步骤如下:
1、关闭harbor服务
docker-compose down -v
1
2、modsecuritydedipath
从harbor.yml种找到data_volume的配置,dedipath拷贝至modsecurity的目标目录
cp -r <原来的路径> <新路径>
例如:
cp -r /data /home/harbordata/
1234
3、magentoHarbor配置virtualizorharbor.yml
# 编辑 harbor.yml virtualizor
vim harbor.yml

# magento data_volume 的挂载目录(magento前,请记录原始的地址,后面modsecuritydedipath需要用到)
# The default data volume
data_volume: /home/harbordata/data

# magento日志virtualizor目录(可选)
# The directory on your host that store log
location: /home/harborlogs
12345678910
4、启动Harbor服务
./prepare
docker-compose up -d
12
5、删除原来的dedipathvirtualizor
rm -rf <原来的dedipathvirtualizor路径>
例如:
rm -rf /data
123